If a broker's JVM garbage collection takes too long, what can occur?

The correct answer is B. ZooKeeper believes the broker to be dead. If the broker's JVM garbage collection (GC) pause is too long, it may fail to send heartbeats to ZooKeeper within the expected interval. As a result, ZooKeeper considers the broker dead, and the broker may be removed from the cluster, triggering leader elections and partition

Monitoring and Troubleshooting

Question

Options

AThere will be a trigger of the broker's log cleaner thread.
BZooKeeper believes the broker to be dead.
CThere is backpressure to, and pausing of, Kafka clients.
DLog files written to disk are loaded into the page cache.

How the community answered

(33 responses)

A
3% (1)
B
70% (23)
C
9% (3)
D
18% (6)

Explanation

If the broker's JVM garbage collection (GC) pause is too long, it may fail to send heartbeats to ZooKeeper within the expected interval. As a result, ZooKeeper considers the broker dead, and the broker may be removed from the cluster, triggering leader elections and partition

Topics

#JVM garbage collection#ZooKeeper session timeout#broker failure#GC pause

Community Discussion

No community discussion yet for this question.

Full CCAAK Practice