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

Maximum replication factor is not considered when assessing whether the cluster is over-provisioned #2170

Closed
bachmanity1 opened this issue Jun 28, 2024 · 0 comments · Fixed by #2171
Closed

Maximum replication factor is not considered when assessing whether the cluster is over-provisioned #2170

bachmanity1 opened this issue Jun 28, 2024 · 0 comments · Fixed by #2171

Comments

@bachmanity1
Copy link
Contributor

While goals such as RackAwareDistributionGoal and RackAwareGoal take the maximum replication factor into account when assessing over-provisioning, other goals do not. This can lead to provision responses that suggest removing brokers, potentially violating the replication factor of certain topics.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Consider max RF when assessing whether the cluster is over-provisioned bachmanity1/cruise-control
1 participant
@bachmanity1