aiquestion commented on PR #12348: URL: https://github.com/apache/kafka/pull/12348#issuecomment-1170703279
@dajac okay, will add ut for it first. It not only happens when A1 is leader and it re-join quickly. If A1 is leader and A2 re-join quickly, other consumer will still revoke their partitions. I refined my example to include a leader: * consumer A1-A10 (ten consumers) joined and synced group successfully with generation 1 **(A1 is the leader)** * New consumer B1 joined and start a rebalance * all consumer joined successfully and then **A1 send syncGroup request and group changed to Stable** * **A2 send syncGroup request, and got assignment which need to revoke partition to transfer to B1** * **A2 do a very quick syncGroup and re-join, because it revoked partition. Group state then changed to PreparingRebalance.** * **A3-A10** didn't send syncGroup before **A2** re-join, so after the send syncGruop, will get REBALANCE_IN_PROGRESS * A3-A10 will revoke there partitions and re-join -- 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]
