search

linkedin / cruise-control

Cruise-control is the first of its kind to fully automate the dynamic workload rebalance and self-healing of a Kafka cluster. It provides great value to Kafka users by simplifying the operation of Kafka clusters.
https://github.com/linkedin/cruise-control/tags
BSD 2-Clause "Simplified" License
2.74k stars 587 forks source link

possibility of having a cluster for cruisecontrol nodes #302

Closed saritago closed 6 years ago

saritago commented 6 years ago

I have a question in similar lines with linkedin/cruise-control#81. What if we really want to have a cluster of CC, how can they both communicate? Does client id(in cruisecontrol.properties file) serve the purpose for treating both the nodes as a part of cluster? When you say alerts are available is that externally configured or some inbuilt option is available for alerting?

efeg commented 6 years ago

Currently each CC instance is expected to be configured such that it manages an exclusive Kafka cluster -- i.e. one-to-one mapping of a CC instance and a Kafka cluster is expected. Hence; as of today, having a cluster of CC instances is not supported. client.id is used for setting the id of metadata client. The alerts mentioned in the issue refers to external alerts for failures of CC instances -- no inbuilt option is available.