CCAAK · Question #38
You manage a Kafka cluster in KRaft mode deployed across multiple data centers. You observed intermittent issues where brokers are frequently leaving the cluster and reconnecting. This is causing…
The correct answer is C. Increase 'brocker.session.timeout.ms' in Controller broker configuration. In KRaft mode, controllers track broker liveness using the broker session timeout. If this timeout is too low for a multi-data-center deployment -- where network latency and temporary delays are common -- brokers may be incorrectly considered dead and removed from the cluster…
Question
You manage a Kafka cluster in KRaft mode deployed across multiple data centers. You observed intermittent issues where brokers are frequently leaving the cluster and reconnecting. This is causing instability in the Kafka environment. Which configuration should you adjust to address this issue?
Options
- AIncrease 'replica..lag.time.max.ms' in the Controller broker configuration file.
- BIncrease 'offsets.commit.timeout.ms' in the Consumer configuration file.
- CIncrease 'brocker.session.timeout.ms' in Controller broker configuration.
- DIncrease 'syncLimit' in the Zookeeper configuration file.
How the community answered
(62 responses)- A3% (2)
- B8% (5)
- C77% (48)
- D11% (7)
Explanation
In KRaft mode, controllers track broker liveness using the broker session timeout. If this timeout is too low for a multi-data-center deployment -- where network latency and temporary delays are common -- brokers may be incorrectly considered dead and removed from the cluster. Increasing broker.session.timeout.ms provides more time for heartbeat processing and prevents unnecessary broker disconnects, stabilizing the cluster.
Topics
Community Discussion
No community discussion yet for this question.