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

new-cluster-enabled and SBR #1075

Open
patriknw opened this issue Oct 10, 2022 · 0 comments
Open

new-cluster-enabled and SBR #1075

patriknw opened this issue Oct 10, 2022 · 0 comments

Comments

@patriknw
Copy link
Member

new-cluster-enabled=false doesn't work well with SBR down-all. It doesn't have to be the down-all SBR strategy but there are also other situations when SBR will resort to downing of all nodes and a new cluster must be formed.

SBR and Cluster Bootstrap are two independent processes so it's not easy to say that new-cluster-enabled should be false unless SBR downed all nodes before the bootstrap.

In Kubernetes it should be safe to use required-contact-point-nr > 1 instead of new-cluster-enabled=false. I haven't even seen any problems with required-contact-point-nr=1.

We should at least document this caveat.

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

No branches or pull requests

1 participant