[ https://issues.apache.org/jira/browse/KAFKA-16299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Kim updated KAFKA-16299: ----------------------------- Description: In the new coordinator, the classic group response handling is not consistent compared to the old coordinator. The old coordinator responds with a NoGeneration id (-1) and an empty members list whereas the new coordinator responds with an empty generation id (0) and a null members list. We should have the new coordinator respond with the same values. Similarly, SyncGroupResponseData#assignment is also populated incorrectly in the case of errors was: In the new coordinator, the classic group response handling is not consistent compared to the old coordinator. The old coordinator responds with a NoGeneration id (-1) and an empty members list whereas the new coordinator responds with an empty generation id (0) and a null members list. We should have the new coordinator respond with the same values. > Classic group error responses should contain a no generation id and an empty > members list > ----------------------------------------------------------------------------------------- > > Key: KAFKA-16299 > URL: https://issues.apache.org/jira/browse/KAFKA-16299 > Project: Kafka > Issue Type: Sub-task > Reporter: Jeff Kim > Assignee: Jeff Kim > Priority: Major > > In the new coordinator, the classic group response handling is not consistent > compared to the old coordinator. > > The old coordinator responds with a NoGeneration id (-1) and an empty members > list whereas the new coordinator responds with an empty generation id (0) and > a null members list. > > We should have the new coordinator respond with the same values. Similarly, > SyncGroupResponseData#assignment is also populated incorrectly in the case of > errors -- This message was sent by Atlassian Jira (v8.20.10#820010)