Kafka medium
A Producer uses `acks=all` (or `-1`). Under which condition will the broker return a 'Success' acknowledgment for a write?
- A As soon as the Leader broker has received the bytes into its network socket buffer.
- B Only after the data has been successfully replicated to the full set of current 'In-Sync Replicas' (ISR).
- C When the message has been read by at least one consumer in the main group.
- D Once the data has been successfully written to the local ZooKeeper metadata store.
Answer: B. Only after the data has been successfully replicated to the full set of current 'In-Sync Replicas' (ISR).
This is the strongest durability guarantee. Combined with `min.insync.replicas`, it ensures that even if the primary node explodes, the data safely exists on other nodes. The trade-off is higher latency compared to `acks=1` (Leader only) or `acks=0` (Fire and forget).
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?