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.

Sign up for GitHub

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

Jump to bottom

Modify startup sequence to match StatefulSet controller's #757

Open
burmanm opened this issue Feb 11, 2025 · 0 comments · May be fixed by #754
Open

Modify startup sequence to match StatefulSet controller's #757

burmanm opened this issue Feb 11, 2025 · 0 comments · May be fixed by #754
Assignees
@burmanm
Labels
enhancement New feature or request

Comments

@burmanm
Copy link
Contributor

burmanm commented Feb 11, 2025 •
edited by sync-by-unito bot
Loading

What is missing?

We currently start pods from the lowest index to highest index (0->2), which does not match the behavior of how StatefulSet controller applies changes (2->0).

Why is this needed?

If user needs to make a change to get cluster to healthy state, we want to start the nodes that have received latest changes first. Currently, they would get started as the last nodes thus potentially leaving us in unfortunate states (for example if the old nodes have issues).

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-90
@burmanm burmanm added the enhancement New feature or request label Feb 11, 2025
@burmanm burmanm linked a pull request Feb 11, 2025 that will close this issue
Draft
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@burmanm burmanm

Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Start sequence burmanm/cass-operator
1 participant
@burmanm