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

Concurrent restarts of previously bootstrapped nodes should be the default #731

Closed
adejanovski opened this issue Nov 15, 2024 · 2 comments · Fixed by #733
Closed

Concurrent restarts of previously bootstrapped nodes should be the default #731

adejanovski opened this issue Nov 15, 2024 · 2 comments · Fixed by #733
Assignees
Labels
enhancement New feature or request

Comments

@adejanovski
Copy link
Contributor

adejanovski commented Nov 15, 2024

What is missing?

We've recently introduced the ability to allow concurrent startup of previously bootstrapped nodes as a feature flag.
This prevents cluster downtime in case one pods fails to restart (because of corrupt sstables for example) and blocks other pods from restarting if they need to.

We'd need to make this the default now and remove the annotation that was used as a feature flag.

Why is this needed?

This feature protects the availability of clusters in case of incidents.

┆Issue is synchronized with this Jira Story by Unito
┆Reviewer: Miles Garnsey
┆Fix Versions: 2024-12
┆Issue Number: CASS-79

@adejanovski adejanovski added the enhancement New feature or request label Nov 15, 2024
@burmanm
Copy link
Contributor

burmanm commented Nov 18, 2024

We'd need to make this the default now and remove the annotation that was used as a feature flag.

I think we should keep the feature flag to allow disabling this behavior, just change evaluation to check for false instead of true.

@adejanovski
Copy link
Contributor Author

I'm ok with that 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: No status
Development

Successfully merging a pull request may close this issue.

2 participants