Kafka medium
In a production environment, which specific event will NOT trigger a 'Consumer Group Rebalance'?
- A A new consumer instance joins the group to help with processing load.
- B A Producer sends a message with an exceptionally large payload (e.g., 5MB) to the topic.
- C An existing consumer crashes or fails to send heartbeats within the `session.timeout.ms` window.
- D The administrator increases the number of partitions for the topic from 10 to 20.
Answer: B. A Producer sends a message with an exceptionally large payload (e.g., 5MB) to the topic.
Rebalancing is about partition assignment. Joining, leaving, or changing the partition count requires a redistribution of work. Producing large messages might cause lag or pressure, but it doesn't change the 'ownership' map of who reads what.
One system design question a day, with spaced repetition so the ones you miss come back.
Get the appRelated questions
- When implementing 'Exactly-Once Semantics' (EOS) in a Kafka stream, what is the role of the `isolation.level=read_committed` setting on the Consumer?
- Historically, which external service was required by Kafka to manage cluster hierarchy, metadata, and leader election status?
- Once a message is successfully appended to a Kafka partition log, what is its mutability status?
- In a Kafka cluster, what is the role of a 'Broker'?
- What is the primary indicator of a bottleneck in a Kafka consumer's processing logic?
- What is the primary architectural role of Apache Kafka in a distributed system?