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

Don't rely on ring replication strategy in repair #4024

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

Michal-Leszczynski
Copy link
Collaborator

@Michal-Leszczynski Michal-Leszczynski commented Sep 5, 2024

Rebased on #4034.

Fixes #4022

@Michal-Leszczynski
Copy link
Collaborator Author

@karol-kokoszka This PR is ready for review!

Copy link
Collaborator

@karol-kokoszka karol-kokoszka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you add some comments to the test cases explaining the scenario and reasoning the output ?

pkg/service/repair/repair_test.go Show resolved Hide resolved
Replication strategy is not returned from Scylla API, but assumed by SM.
That's why we shouldn't rely on it.

Fixes #4022
@Michal-Leszczynski
Copy link
Collaborator Author

@karol-kokoszka I added requested explanations.

Copy link
Collaborator

@karol-kokoszka karol-kokoszka left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@Michal-Leszczynski Michal-Leszczynski merged commit 9cb43f8 into master Sep 26, 2024
51 checks passed
@Michal-Leszczynski Michal-Leszczynski deleted the ml/fix-4022 branch September 26, 2024 11:40
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.

Don't rely on ring replication strategy in repair
2 participants