banzaicloud/koperator

CruiseControl

tony-chen1-rh opened this issue · 8 comments

tony-chen1-rh commented

I see the following warnings in my kafka broker pod. How can I fix this? Does this prevent additional brokers from spinning up? I am installing https://github.com/banzaicloud/koperator/blob/v0.11.1/config/samples/simplekafkacluster.yaml with our own zookeeper cluster.

...
[2022-06-04 00:16:23,977] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17090 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,078] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17091 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,178] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17092 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,279] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17093 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,380] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17094 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,480] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17095 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,581] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17096 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,681] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17097 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,781] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17098 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,882] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17099 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
[2022-06-04 00:16:24,982] WARN [Producer clientId=CruiseControlMetricsReporter] Error while fetching metadata with correlation id 17100 : {__CruiseControlMetrics=UNKNOWN_TOPIC_OR_PARTITION} (org.apache.kafka.clients.NetworkClient)
...
stoader commented

@piotrzbq can you provide more detail as from your comment is unclear what issue you're facing with.

piotrzbq commented

I have noticed same warnings for kafka producer when specific topic didn't exist, so try to create one as in example.

stoader commented

The UNKNOWN_TOPIC_OR_PARTITION usually means that the topic is missing or partition leader is not reachable (which can be caused by network issues). In case of CruiseControl the topic is created by CruiseControl itself in newer version that's why I suggested using the latest koperator version which deploys newer CC version.

tony-chen1-rh commented

@stoader with v0.11.1, I was able to get past this error after I set headlessServiceEnabled to false. This probably had something to do with how our kubernetes clusters were set up. Once every broker had their own ClusterIP, the brokers could communicate with each other and all 3 brokers in simplekafkacluster.yaml came up.

tony-chen1-rh commented

I'll close this issue since no further action is needed. Thanks.