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

ScyllaDB 5.2 nodes are created out of compliance with docs #280

Open
lattwood opened this issue Aug 8, 2023 · 1 comment
Open

ScyllaDB 5.2 nodes are created out of compliance with docs #280

lattwood opened this issue Aug 8, 2023 · 1 comment

Comments

@lattwood
Copy link

lattwood commented Aug 8, 2023

Generally a "new default" is created by changing the default value used when decoding the config that is used in the absence of the value- not changing a config variable in a shipped configuration file.

This isn't an issue with this project but it's an issue with ScyllaDB's communication with downstream consumers/orchestrators, such as this ansible role.

https://www.scylladb.com/2023/05/04/scylladbs-path-to-strong-consistency-a-new-milestone/

image
@tarzanek
Copy link
Collaborator

consistent_cluster_management: true

should be added to scylla.yaml template

and ev. check if –consistent-cluster-management command line option to scylla binary is needed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants