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

Add an option to skip the forced cluster start operation during scaling out #729

Closed
AstroProfundis opened this issue Aug 29, 2020 · 1 comment
Labels
category/stability Categorizes issue or PR as a stability enhancement. category/usability Categorizes issue or PR as a usability enhancement. status/TODO Categorizes issue as we will do it. type/enhancement Categorizes issue or PR as related to an enhancement. type/feature-request Categorizes issue as related to a new feature.
Milestone

Comments

@AstroProfundis
Copy link
Contributor

AstroProfundis commented Aug 29, 2020

Feature Request

Is your feature request related to a problem? Please describe:

We observed a case (#730) that the "start cluster" might fail on some certain environment if the cluster has large amount instances, and if it fails to start the cluster, the whole scale out process is interrupted.

Describe the feature you'd like:

If the cluster can be confirmed to be already started, the "start cluster" operation could be safely skipped, but we don't have that option for user now.

Describe alternatives you've considered:

It's also possible to use a -f/--force flag to skip all operations that not critically necessary during an operation, like various checks or preparations. This could be a more generic solution.

Teachability, Documentation, Adoption, Migration Strategy:

@AstroProfundis AstroProfundis added type/feature-request Categorizes issue as related to a new feature. category/stability Categorizes issue or PR as a stability enhancement. category/usability Categorizes issue or PR as a usability enhancement. status/TODO Categorizes issue as we will do it. type/enhancement Categorizes issue or PR as related to an enhancement. labels Aug 29, 2020
@lucklove lucklove added this to the v1.3.0 milestone Sep 15, 2020
@lucklove
Copy link
Member

We don't auto-start the cluster since #848

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category/stability Categorizes issue or PR as a stability enhancement. category/usability Categorizes issue or PR as a usability enhancement. status/TODO Categorizes issue as we will do it. type/enhancement Categorizes issue or PR as related to an enhancement. type/feature-request Categorizes issue as related to a new feature.
Projects
None yet
Development

No branches or pull requests

2 participants