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

[Multi-DC] Cleanup shouldn't be run on every scaling event #2264

Open
Tracked by #2230
ylebi opened this issue Dec 12, 2024 · 0 comments
Open
Tracked by #2230

[Multi-DC] Cleanup shouldn't be run on every scaling event #2264

ylebi opened this issue Dec 12, 2024 · 0 comments
Assignees
@zimnx
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Milestone
v1.17.0

Comments

@ylebi
Copy link
Collaborator

ylebi commented Dec 12, 2024 •
edited
Loading

Modify cleanup behavior during scaling. For multi-DC clusters, cleanup should run only after scaling is completed rather than after each node addition.
@ylebi ylebi mentioned this issue Dec 12, 2024
Open
@scylla-operator-bot scylla-operator-bot bot added the needs-priority Indicates a PR lacks a `priority/foo` label and requires one. label Dec 12, 2024
@ylebi ylebi added kind/feature Categorizes issue or PR as related to a new feature. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. kind/bug Categorizes issue or PR as related to a bug. and removed needs-priority Indicates a PR lacks a `priority/foo` label and requires one. kind/feature Categorizes issue or PR as related to a new feature. labels Dec 12, 2024
@zimnx zimnx self-assigned this Dec 12, 2024
@ylebi ylebi changed the title Cleanup shouldn't be run on every scaling event [Multi-DC] Cleanup shouldn't be run on every scaling event Dec 15, 2024
@zimnx zimnx added this to the v1.17.0 milestone Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@zimnx zimnx

Labels
kind/bug Categorizes issue or PR as related to a bug. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete.
Projects
None yet
Milestone
v1.17.0
Development

No branches or pull requests
2 participants
@zimnx @ylebi