Guozhang Wang created KAFKA-8487:
------------------------------------
Summary: Consumer should not resetGeneration upon
REBALANCE_IN_PROGRESS in commit response handler
Key: KAFKA-8487
URL: https://issues.apache.org/jira/browse/KAFKA-8487
Project: Kafka
Issue Type: Improvement
Components: consumer
Reporter: Guozhang Wang
Assignee: Guozhang Wang
In consumer, we handle the errors in sync / heartbeat / join response such that:
1. UNKNOWN_MEMBER_ID / ILLEGAL_GENERATION: we reset the generation and request
re-join.
2. REBALANCE_IN_PROGRESS: do nothing if a rejoin will be executed, or request
re-join explicitly.
However, for commit response, we require resetGeneration for
REBALANCE_IN_PROGRESS as well. This is a flaw in two folds:
1. As in KIP-345, with static members, reseting generation will lose the
member.id and hence may cause incorrect fencing.
2. As in KIP-429, resetting generation will cause partitions to be "lost"
unnecessarily before re-joining the group.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
