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

Improve safety of replace #386

Open
burmanm opened this issue Jul 29, 2022 · 0 comments
Open

Improve safety of replace #386

burmanm opened this issue Jul 29, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@burmanm
Copy link
Contributor

burmanm commented Jul 29, 2022

What is missing?
At the moment, it is possible for us to start replacing more nodes than the cluster can in reality handle. This is because we continue with the replace process of the next node before the first one has actually streamed all the data from other nodes.

The safety of this process is at the hands of the user, however a user-mistake could put the cluster in danger of losing availability (or worse).

Why do we need it?

Environment

  • Cass Operator version:

    Insert image tag or Git SHA here

    **Anything else we need to know?**:

┆Issue is synchronized with this Jira Story by Unito
┆Issue Number: CASS-36

@burmanm burmanm added the enhancement New feature or request label Jul 29, 2022
@sync-by-unito sync-by-unito bot changed the title Improve safety of replace / restarts K8SSAND-1708 ⁃ Improve safety of replace / restarts Jul 29, 2022
@burmanm burmanm changed the title K8SSAND-1708 ⁃ Improve safety of replace / restarts K8SSAND-1708 ⁃ Improve safety of replace Aug 23, 2022
@adejanovski adejanovski moved this to To Groom in K8ssandra Nov 8, 2022
@sync-by-unito sync-by-unito bot changed the title K8SSAND-1708 ⁃ Improve safety of replace Improve safety of replace Oct 11, 2024
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

No branches or pull requests

1 participant