cruise-control
cruise-control copied to clipboard
Warnings When Running in Kafka Cluster
Running Cruise Control in a Kafka cluster and getting warnings. Should I be concerned about these warnings? Here is a sample:
ConsumerConfig:384 - The configuration 'broker.metrics.window.ms' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN ConsumerConfig:384 - The configuration 'metric.anomaly.finder.class' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN ConsumerConfig:384 - The configuration 'linear.regression.model.min.num.cpu.util.buckets' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN ConsumerConfig:384 - The configuration 'sample.partition.metric.store.on.execution.class' was supplied but isn't a known config. ProducerConfig:384 - The configuration 'topic.replica.count.balance.max.gap' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN ProducerConfig:384 - The configuration 'config.providers.env.class' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN ProducerConfig:384 - The configuration 'metadata.factor.exponent' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN ProducerConfig:384 - The configuration 'partition.metric.sample.store.topic' was supplied but isn't a known config. AdminClientConfig:384 - The configuration 'min.topic.leaders.per.broker' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN AdminClientConfig:384 - The configuration 'anomaly.detection.goals' was supplied but isn't a known config. 2024-01-23 14:37:40 WARN AdminClientConfig:384 - The configuration 'min.valid.partition.ratio' was supplied but isn't a known config.
Is there any update on this issue? Thanks
I wouldn't worry about those warnings since they don't have any effects. However it seems like you are passing cruise control configs into your kafka producer/consumer, which is wrong.