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

Fix cluster name check in repair concurrency control #1320

Merged
merged 1 commit into from
Jul 19, 2023

Conversation

adejanovski
Copy link
Contributor

Fixes #1319

An == operator was used to filter the active RepairRunner instances based on the cluster name.
That will obviously give unexpected results, which was allowing all repairs to run concurrently instead of respecting the maxParallelRepairs limit.

This is fixed by this PR and the code that applies the filtering has been refactored to allow it being tested.

@adejanovski adejanovski self-assigned this Jul 17, 2023
@adejanovski adejanovski marked this pull request as ready for review July 17, 2023 10:01
@adejanovski adejanovski force-pushed the fix-concurrent-repairs-cluster-compare branch from ad03e1e to 391d74a Compare July 17, 2023 12:39
@burmanm burmanm self-requested a review July 18, 2023 12:28
burmanm
burmanm previously approved these changes Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

maxParallelRepair setting is not getting respected by Reaper
2 participants