[ https://issues.apache.org/jira/browse/KAFKA-15763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jacot resolved KAFKA-15763. --------------------------------- Resolution: Won't Fix We went with another approach. > Group Coordinator should not deliver new assignment before previous one is > acknowledged > --------------------------------------------------------------------------------------- > > Key: KAFKA-15763 > URL: https://issues.apache.org/jira/browse/KAFKA-15763 > Project: Kafka > Issue Type: Sub-task > Reporter: David Jacot > Assignee: David Jacot > Priority: Major > > In the initial implementation of the new consumer group protocol, the group > coordinators waits on received an acknowledgement from the consumer only when > there are partitions to be revoked. In the case of newly assigned partitions, > a new assignment can be delivered any time (e.g. in two subsequent > heartbeats). > While implementing the state machine on the client side, we found out that > this caused confusion because the protocol does not treat revocation and > assignment in the same way. We also found out that changing the assignment > before the previous one is fully processed by the member makes the client > side logic more complicated than it should be because the consumer can't > process any new assignment until it has completed the previous one. > In the end, it is better to change the server side to not deliver a new > assignment before the current one is acknowledged by the consumer. -- This message was sent by Atlassian Jira (v8.20.10#820010)