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

[Improvement] Restart cluster components with order defined in ClusterDefinition #7648

Open
nayutah opened this issue Jun 27, 2024 · 1 comment
Assignees
Labels
kind/enhancement New feature or request

Comments

@nayutah
Copy link
Collaborator

nayutah commented Jun 27, 2024

Is your improvement request related to a problem? Please describe.
When restart a cluster, restart the component one by one and following the order defined in ClusterDefinition, this can avoid many concurrency problems. For clusters with more than one interdependent components, like sentinel redis and orchestrator mysql, it is a practical way to make the cluster more robust.
For reconfigure/vscale operation that may incur restarts, it should also follow the defined component orders.

@nayutah nayutah added the kind/enhancement New feature or request label Jun 27, 2024
@nayutah
Copy link
Collaborator Author

nayutah commented Jun 27, 2024

also helps to fix #7519

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants