Known issues in Cruise Control
Learn about the known issues in Cruise Control, the impact or changes to the functionality, and the workaround.
- CDPD-47616: Unable to initiate rebalance, number of valid windows (NumValidWindows) is zero
- If a Cruise Control rebalance is initiated with the
rebalance_disk
parameter and Cruise Control is configured to fetch metrics from Cloudera Manager (Metric Reporter is set to CM metrics reporter), Cruise Control stops collecting metrics from the partitions that are moved. This is because Cloudera Manager does not collect metrics from moved partitions due to an issue in Kafka (KAFKA-10320).If the metrics are not available, the partition is considered invalid by Cruise Control. This results in Cruise Control blocking rebalance operations and proposal generation.
- OPSAPS-68148: Cruise Control rack aware goal upgrade handler
- The goal sets in Cruise Control, which include the default, supported, hard, self-healing and anomaly detection goals, might be overridden to their default value after a cluster upgrade if the goals have been customized.
- OPSAPS-66432: Cruise Control does not start with Python 3
- When installing Cruise Control with Python 3 as the default Python
version, Cruise Control will fail to start with the following error due to Python 2
compatibility in the CSD script of Cruise
Control:
File "/var/run/cloudera-scm-agent/process/1546350171-cruise_control-CRUISE_CONTROL_SERVER/scripts/capacity.py", line 185, in create_capacities_json
- OPSAPS-69978: Cruise Control capacity.py script fails on Python 3
-
Cruise Control might fail to start on Python 3 when capacity information is queried during the startup process. This is caused by a breaking change between Python 2 and 3.