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

Await schema agreement returns wrong error #70

Closed
mmatczuk opened this issue Dec 18, 2020 · 1 comment · Fixed by #256
Closed

Await schema agreement returns wrong error #70

mmatczuk opened this issue Dec 18, 2020 · 1 comment · Fixed by #256
Assignees

Comments

@mmatczuk
Copy link

Schema is in sync no schema changes events, it detects no conflicts yet still error is returned.

15:40:56.285    INFO    backup.await_schema     Awaiting schema agreement...
15:42:56.427    INFO    backup.await_schema     Schema agreement error  {"error": "gocql: cluster schema versions not consistent: []"}
15:42:56.428    INFO    backup.await_schema     Schema agreement not reached, retrying...       {"error": "gocql: cluster schema versions not consistent: []", "wait": "16.538893946s"}
15:45:13.126    INFO    backup.await_schema     Schema agreement error  {"error": "gocql: cluster schema versions not consistent: []"}
15:45:13.126    INFO    backup.await_schema     Schema agreement not reached, retrying...       {"error": "gocql: cluster schema versions not consistent: []", "wait": "29.401847101s"}
15:47:42.684    INFO    backup.await_schema     Schema agreement error  {"error": "gocql: cluster schema versions not consistent: []"}
15:47:42.684    INFO    backup.await_schema     Schema agreement not reached, retrying...       {"error": "gocql: cluster schema versions not consistent: []", "wait": "56.135457321s"}
@mmatczuk
Copy link
Author

It can happen when Session is closed. This is a rare case but still behaviour is not correct.

@mmatczuk mmatczuk changed the title Await schema agreement is broken Await schema agreement returns wrong error Dec 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants