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

Consider max RF when assessing whether the cluster is over-provisioned #2171

Merged
merged 6 commits into from
Jul 11, 2024

Conversation

bachmanity1
Copy link
Contributor

This PR resolves #2170.

@bachmanity1
Copy link
Contributor Author

@CCisGG @efeg @hshi2022 can you please have a look?

Copy link
Contributor

@CCisGG CCisGG left a comment

Choose a reason for hiding this comment

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

Left a non-blocking comment. This change looks reasonble to me. Thanks @bachmanity1 !

@bachmanity1 bachmanity1 requested a review from CCisGG July 8, 2024 20:29
@bachmanity1
Copy link
Contributor Author

@CCisGG can we get this merged?

@CCisGG CCisGG merged commit 21a4f3f into linkedin:main Jul 11, 2024
2 checks passed
@bachmanity1 bachmanity1 deleted the fix-overprovisioned branch July 11, 2024 23:58
trancodyy pushed a commit to DataDog/cruise-control that referenced this pull request Sep 6, 2024
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.

Maximum replication factor is not considered when assessing whether the cluster is over-provisioned
2 participants