max.poll.interval.ms
The consumer setting for the longest gap allowed between two poll calls before the consumer is treated as stuck and removed from the group.
In more detail
Heartbeats prove the process is alive, but this limit proves it is making progress. Slow work inside the loop, such as a slow database write, can exceed it and trigger a rebalance even while heartbeats continue. The default is 300000 milliseconds.
Related terms
- poll loop — The loop in which a consumer repeatedly asks the broker for new records and processes them.
- session.timeout.ms — The consumer setting for how long the group coordinator waits without a heartbeat before declaring the consumer dead and rebalancing.
- rebalance — The process in which a consumer group redistributes partitions among its members after one joins, leaves or is judged dead.
Taught in
- Too Slow Between Two Polls — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- The Alert That Came An Hour Late — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Eleven Thousand Scans That Never Arrived — Confluent Apache Kafka Certifications (CCDAK and CCAAK) Exam Prep
- Rebalancing And Its Cost — Apache Kafka & Event Streaming