-
Notifications
You must be signed in to change notification settings - Fork 29
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
Cluster check should be configurable with an expected number of nodes #42
Comments
Making the cluster check optional #35 would prevent this issue and more generally the issue of applying schema upgrades when 1 node is down. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We ran into a problem where we replaced some cassandra nodes. The cluster was perfectly fine, but the old nodes were still in the
system.peers
table. So the migration failed, since it saw the old dead node as unhealthy.I'd prefer if:
I think that should be sufficient to give us confidence that a schema change is safe to apply. The drawback is it adds more configuration - perhaps a simplification is to just check that a quorum of
getAllHosts
is available, rather than all of them.The text was updated successfully, but these errors were encountered: