Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'innodb_snapshot_isolation' can't be set to the value of 'READ-UNCOMMITTED' #844

Open
Xoshbin opened this issue Jun 7, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Xoshbin
Copy link

Xoshbin commented Jun 7, 2024

Gorse version
Latest
Describe the bug
Suddenly I'm receiving this error, I tried many ways but so far could not solve it,

ERROR failed to initialize database, got error Error 1231: Variable 'innodb_snapshot_isolation' can't be set to the value of 'READ-UNCOMMITTED'
2024-06-07T18:10:53.279Z FATAL failed to connect data database {"error": "Error 1231: Variable 'innodb_snapshot_isolation' can't be set to the value of 'READ-UNCOMMITTED'", "errorVerbose": "Error 1231: Variable 'innodb_snapshot_isolation' can't be set to the value of 'READ-UNCOMMITTED'\ngithub.com/zhenghaoz/gorse/storage/data.Open:176:
To Reproduce
After restarting the server and running the gorse command the error appeared.

@Xoshbin Xoshbin added the bug Something isn't working label Jun 7, 2024
@Xoshbin
Copy link
Author

Xoshbin commented Jun 28, 2024

Is it possible to add "innodb_snapshot_isolation" to optional in the config.tom file or it's required?!
Because in a situation like mine I can't change the innodb_snapshot_isolation to READ-UNCOMMITTED on the server side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant