Known issues in Cruise Control
This topic describes known issues for using Cruise Control in this release of Cloudera Runtime.
Cruise Control might fail at first run
When you install Cruise Control either individually or using the Compute Cluster - StreamingMessaging(Full) deployment, Cruise Control might fail at the first run. This is caused by the difference between the Security Protocol in Kafka and in Cruise Control.
To avoid and solve this issue, see the Add Cruise Control documentation.
OPSAPS-58700: Cruise Control capacity bootstrapping ignores deleted log directories
Log directories remain in the metrics database after a log directory is removed from Kafka. This causes Cruise Control unable to start up as it tries to query the metrics in Cloudera Manager without any data in them.
Workaround: You need to stop the service monitor and delete the database (by default it
can be found at: /var/lib/cloudera-service-monitor). Restart the service
monitor and also Cruise Control.
CDPD-10505: Cruise Control does not package cruise-control-version.properties
The python client cannot be used as Cruise Control does not give any version information in
HTTP response headers. In this version, Cruise Control does not support generating the
cruise-control-version.properties file that is required by the python client
for compatibility checks.
