intermediateConsumer Timing Configurations
What does `max.poll.interval.ms` actually protect against, and what happens if a consumer exceeds it?
It's the maximum time allowed between successive calls to `poll()` — if your processing logic between polls takes longer than this (e.g. a slow downstream call), Kafka assumes the consumer instance is stuck or dead and triggers a rebalance, reassigning its partitions to other consumers, which can cause the 'stuck' consumer to have its work duplicated once it finally does respond.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response