Time taking for Kafka for being non-operational when zk is down. #10008
Unanswered
m2khosravi
asked this question in
Q&A
Replies: 2 comments 3 replies
-
In general, ZooKeeper failure might not cause any immediate issues to the Kafka cluster. But might break it for example when a failover happens, creation of new topics etc. I'm not sure how exactly do you run the command you shared above, but if you do it from the Kafka pod, I would never expect it to work ZooKeeper or not as it does not authenticate etc. |
Beta Was this translation helpful? Give feedback.
3 replies
-
Any thoughts on that? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Team,
I conducted a test scenario by shutting down the zk node, and I observed that the following command received a response:
kafka-topics --bootstrap-server localhost:9091 --list strimzi.cruisecontrol.metrics strimzi.cruisecontrol.modeltrainingsamples strimzi.cruisecontrol.partitionmetricsamples
However, after a couple of minutes, the execution failed, and recognized the zk issue. The time it takes for this failure varies. Could you please help me understand the main reason for this variability? Additionally, can we tune or modify parameters to enable Kafka to detect zk failures more efficiently and fail such commands?
Your assistance would be greatly appreciated,
Mahdi
Beta Was this translation helpful? Give feedback.
All reactions