[jira] [Created] (KAFKA-13126) Overflow in joinGroupTimeoutMs when max.poll.interval.ms is MAX_VALUE leads to missing rebalances

["A. Sophie Blee-Goldman (Jira)" <ji...@apache.org>]

A. Sophie Blee-Goldman created KAFKA-13126:
----------------------------------------------

             Summary: Overflow in joinGroupTimeoutMs when max.poll.interval.ms is MAX_VALUE leads to missing rebalances
                 Key: KAFKA-13126
                 URL: https://issues.apache.org/jira/browse/KAFKA-13126
             Project: Kafka
          Issue Type: Bug
          Components: consumer
            Reporter: A. Sophie Blee-Goldman
            Assignee: A. Sophie Blee-Goldman
             Fix For: 3.1.0


In older versions of Kafka Streams, the {{max.poll.interval.ms}} config was overridden by default to {{Integer.MAX_VALUE}}. Even after we removed this override, users of both the plain consumer client and kafka streams still set the poll interval to MAX_VALUE somewhat often. Unfortunately, this causes an overflow when computing the {{joinGroupTimeoutMs}} and results in it being set to the {{request.timeout.ms}} instead, which is much lower.

This can easily make consumers drop out of the group, since they must rejoin now within 30s (by default) yet have no obligation to almost ever call poll() given the high {{max.poll.interval.ms}}. We just need to check for overflow and fix it to {{Integer.MAX_VALUE}} when it occurs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)