[KAFKA-13214] Consumer should not reset group state after disconnect

• Type: Bug
• Status: Resolved
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 2.7.0, 2.8.0
• Fix Version/s: 2.7.2, 2.8.1, 3.0.0
• Labels: new-consumer-threading-should-fix
• Assignee: Jason Gustafson
• Reporter: Jason Gustafson
• Created: 18/Aug/21 16:23
• Updated: 06/Jun/22 21:11
• Resolved: 24/Aug/21 19:05

Description

When the consumer disconnects from the coordinator while a rebalance is in progress, we currently reset the memberId and generation. The coordinator then must await the session timeout in order to expire the old memberId. This was apparently a regression from https://github.com/apache/kafka/commit/7e7bb184d2abe34280a7f0eb0f0d9fc0e32389f2#diff-15efe9b844f78b686393b6c2e2ad61306c3473225742caed05c7edab9a138832R478. It would be better to keep the memberId/generation.

Issue Links

• links to: GitHub Pull Request #11231