Kafka - Cluster Architecture
You are implementing a Kafka monitoring tool that must detect and log whenever the controller broker changes. Which method correctly achieves this using Kafka's AdminClient?
You are implementing a Kafka monitoring tool that must detect and log whenever the controller broker changes. Which method correctly achieves this using Kafka's AdminClient?
hard📝 Application Q8 of 15
Step-by-Step Solution
Solution:
Step 1: Identify how to detect controller changes
Kafka AdminClient'sdescribeCluster().controller()returns the current controller broker node.Step 2: Implement monitoring logic
By polling this method periodically and comparing the returned controller ID with the previous one, changes can be detected and logged.Step 3: Evaluate other options
Subscribe to a Kafka topic that emits controller change events automatically is invalid as Kafka does not emit controller change events to topics by default. Use ZooKeeper watchers to listen for controller changes without AdminClient uses ZooKeeper, which is deprecated in newer Kafka versions. Restart the AdminClient periodically to refresh controller information is inefficient and does not detect changes promptly.Final Answer:
Continuously poll adminClient.describeCluster().controller() and compare the controller ID to detect changes -> Option DQuick Check:
Polling controller info detects changes reliably [OK]
Quick Trick: Poll controller info repeatedly to detect changes [OK]
Common Mistakes:
- Expecting Kafka to publish controller changes to a topic
- Relying solely on ZooKeeper in newer Kafka versions
- Restarting AdminClient instead of polling
Master "Cluster Architecture" in Kafka
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kafka Quizzes