We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In #496 we removed the functionality that would wait for cleanup to finish after scale up before marking the process as done.
We want to return this behavior, but as an optional one.
If after scaling up (without cleanup) a scale down is used, it is possible to introduce ghost data back to the cluster.
┆Issue is synchronized with this Jira Story by Unito ┆Reviewer: Alexander Dejanovski ┆Fix Versions: 2024-11 ┆Issue Number: CASS-76
The text was updated successfully, but these errors were encountered:
burmanm
Successfully merging a pull request may close this issue.
What is missing?
In #496 we removed the functionality that would wait for cleanup to finish after scale up before marking the process as done.
We want to return this behavior, but as an optional one.
Why is this needed?
If after scaling up (without cleanup) a scale down is used, it is possible to introduce ghost data back to the cluster.
┆Issue is synchronized with this Jira Story by Unito
┆Reviewer: Alexander Dejanovski
┆Fix Versions: 2024-11
┆Issue Number: CASS-76
The text was updated successfully, but these errors were encountered: