Adem Efe Gencer
Adem Efe Gencer
"... load monitor does not have enough snapshots" -> It is likely that your Cruise Control instance fails to collect metrics. There should be some relevant messages on (1) Cruise...
Your broker logs show no indication of being configured properly to work with CruiseControlMetrics reporter. Please follow the steps documented in the [Quick Start](https://github.com/linkedin/cruise-control#quick-start). In particular, please make sure that...
> @efeg : is it necessary that the broker should be on the same java version as cruise control as the section of the quick start that says "Modify Kafka...
@kyguy This seems like a useful change -- thanks for bringing this up and proposing to contribute!
cruise control can't recognize topics which are newly created during the execution of remove_broker?
@jiao-zhangS Thanks for creating the issue. This is not an expected behavior -- i.e. `kafka_cluster_state` should always show the latest metadata and any followup removal should remove replicas (if any)...
cruise control can't recognize topics which are newly created during the execution of remove_broker?
@jiao-zhangS Created #1726 and linked this issue to it. Recreating a topic with the same name may indeed cause this issue, and we will address that on CC. Once again,...
@tomncooper Thanks for sharing the KIP -- I agree that CC can help with the initial assignment of partitions. I commented on the relevant thread in `kafka-dev` mailing list.
@emelyanovtv I am curious what the `load` endpoint of Cruise Control shows with `populate_disk_info=true`. I wonder if the same disk is used by other services, causing the capacity to be...
@kyguy Thanks for the proposal and offer for contribution! I see the intention is to make it easier for users to resolve the capacity of brokers. To achieve that, I'd...
@CR-AvrahamKalvo Which version of Kafka are you using? The following exception indicates that the issue is on Kafka controler-side -- so deleting CC topic zNodes is not the solution (in...