Shawn Wang created KAFKA-14016:
----------------------------------
Summary: Revoke more partitions than expected in Cooperative
rebalance
Key: KAFKA-14016
URL: https://issues.apache.org/jira/browse/KAFKA-14016
Project: Kafka
Issue Type: Bug
Components: clients
Affects Versions: 3.3.0
Reporter: Shawn Wang
In https://issues.apache.org/jira/browse/KAFKA-13419 we found that some
consumer didn't reset generation and state after sync group fail with
REABALANCE_IN_PROGRESS error.
So we fixed it by reset generationId (no memberId) when sync group fail with
REABALANCE_IN_PROGRESS error.
But this change missed the reset part, so another change made in
https://issues.apache.org/jira/browse/KAFKA-13891 make this works.
After apply this change, we found that: sometimes consumer will revoker almost
1/3 of the partitions with cooperative enabled. Because if a consumer did a
very quick re-join, other consumers will get REABALANCE_IN_PROGRESS in
syncGroup and revoked their partition before re-jion.
I think the whole history is : in Cooperative rebalance, we found a duplicate
assign bug https://issues.apache.org/jira/browse/KAFKA-12984 and have several
fixes:
#
https://issues.apache.org/jira/browse/KAFKA-12983
*
**
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
