You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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
The text was updated successfully, but these errors were encountered: