sanghyeok An created KAFKA-21303:
------------------------------------
Summary: Incorrect session timeout applied to classic members when
reloading a consumer group
Key: KAFKA-21303
URL: https://issues.apache.org/jira/browse/KAFKA-21303
Project: Kafka
Issue Type: Bug
Reporter: sanghyeok An
Assignee: sanghyeok An
When a consumer group contains members using the classic protocol, reloading
the group applies the consumer protocol session timeout to those members
instead of their persisted session timeouts.
A classic member's session timeout is provided in its JoinGroup request and
persisted in the member metadata. However, GroupMetadataManager.onLoaded()
ignores this value and applies the consumer protocol session timeout to every
member of the consumer group.
For example, if a classic member's session timeout is 10 seconds and the
consumer protocol session timeout is 45 seconds, reloading the group after a
coordinator change schedules the member's expiration for 45 seconds later. If
the member sends no further heartbeats, failure detection and partition
reassignment may be delayed.
Conversely, if the classic member's session timeout is 60 seconds and the
consumer protocol session timeout is 45 seconds, the member may be removed
before its configured timeout elapses if its next heartbeat has not yet arrived.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
