Consumer rebalance triggered by max.poll.interval.ms timeout during long-running record processing
When a Kafka consumer processes record batches that exceed the configured max.poll.interval.ms (default 5 minutes), the consumer proactively leaves the group and triggers a rebalance. This behavior is by design to detect stalled consumers, but it creates a tension with workloads that legitimately require extended per-record processing time, such as complex t
apachekafka