-
Notifications
You must be signed in to change notification settings - Fork 34
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
Restore schema workaround #3697
Conversation
…ndpoint This endpoint returns 'consistent_cluster_management' option from scylla.yaml.
eedbf52
to
5100e4e
Compare
5100e4e
to
dbc72c9
Compare
In the logs of
|
This PR contains workaround documentation for bot Scylla 5.4 and 2024, even though the latter one is not released yet. Is this ok? It also adds Scylla 5.4 into restore compatibility matrix. Should Scylla 2024 be added there as well? |
@karol-kokoszka @annastuchlik @tzach could you take a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍 LGTM
@tzach @annastuchlik could you please take a look? |
a42219a
to
1e75e01
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM (docs)
This PR adds a validation of
consistent_cluster_management
and Scylla version before restoring schema (more info in #3662). It also documents a workaround for newer Scylla versions withconsistent_cluster_management: true
.