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

Cruise Control with MSK - Not able to remove broker due to capacity limit #2210

Open
danielap-ma opened this issue Oct 23, 2024 · 0 comments

Comments

@danielap-ma
Copy link

Hello,

I've connected Cruise Control to my MSK cluster, and the metrics are drawn from Prometheus.
When I try to disconnect a broker, no matter which hard goal I set, the operation fails due to insufficient capacity. Example:

ERROR: Error processing POST request '/remove_broker' due to: 'com.linkedin.kafka.cruisecontrol.exception.OptimizationFailureException: [DiskCapacityGoal] Utilization (137393.11) of broker 2 violated capacity limit (-0.99) for resource disk. Add at least 1 broker for disk. Add at least 1 broker for disk.'.

The disk usage is less than 140GB, and the broker disk size is 310GB.

Even when the usage is 0 like with Network Outbound metrics, I get the same error:

ERROR Error processing POST request '/remove_broker' due to: 'com.linkedin.kafka.cruisecontrol.exception.OptimizationFailureException: [NetworkOutboundCapacityGoal] Utilization (0.00) of host b-2.XXXXX.kafka.us-east-1.amazonaws.com violated capacity limit (-0.80) for resource networkOutbound. Add at least 1 broker for networkOutbound. Add at least 1 broker for networkOutbound.'. (com.linkedin.kafka.cruisecontrol.KafkaCruiseControlRequestHandler)

Any idea what could be the issue here?

Thank you

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

No branches or pull requests

1 participant