Kafka easy
What is the primary indicator of a bottleneck in a Kafka consumer's processing logic?
- A Increasing network packet loss between the client and the switch.
- B The amount of free disk space on the consumer's local machine.
- C Consumer Lag: The numerical difference between the latest offset written to the topic and the latest offset successfully processed by the consumer.
- D The number of open TCP connections in the TIME_WAIT state.
Answer: C. Consumer Lag: The numerical difference between the latest offset written to the topic and the latest offset successfully processed by the consumer.
Lag is the most important metric for health. High lag means the consumer is not fast enough to handle the incoming stream. This is common if the processing logic is heavy or if the consumer is waiting on a slow external database.
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 architectural role of Apache Kafka in a distributed system?
- When a Producer sends a message with a specific 'Key', how does Kafka interpret this for shard distribution?