dajac commented on PR #12348: URL: https://github.com/apache/kafka/pull/12348#issuecomment-1168677703
@aiquestion Thanks for the patch. Before settling in on the best approach to fix this, could we start by adding a unit test which reproduces the issue? Could you explain why we need to revert https://issues.apache.org/jira/browse/KAFKA-13891? In the scenario you describe in the Jira: - consumer A1-A10 (ten consumers) joined and synced group successfully with generation 1 - New consumer B1 joined and start a rebalance - all consumer joined successfully and then A1 need to revoke partition to transfer to B1 - A1 do a very quick syncGroup and re-join, because it revoked partition - A2-A10 didn't send syncGroup before A1 re-join, so after the send syncGruop, will get REBALANCE_IN_PROGRESS - A2-A10 will revoke there partitions and re-join I suppose that this scenario only works if A1 is the leader, right? Otherwise, A1 would not have received the sync group response. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
