Hi TengYao, Thanks for writing up this KIP :)
Questions: KT1: Why would a non-Kafka Streams application want to set leaveGroup=false? Because Kafka Streams manages the group membership assignment under the covers, it can re-assign partitions to a new Consumer when the old one closes. But in a non-Kafka Streams application, doesn’t this just leave the partitions assigned until the coordinator kicks the member out of the group? KT2: Can you add the actual API changes to the KIP? KT3: Does setting leaveGroup=true carry the *guarantee* that the member will leave the group? I’m currently battling some edge cases where close() is called with a zero timeout and it times out before the consumer can leave the group cleanly. Thanks, Kirk > On Sep 22, 2024, at 9:26 PM, TengYao Chi <kiting...@gmail.com> wrote: > > Hello everyone, > > I would like to start a discussion thread on KIP-1092 > <https://cwiki.apache.org/confluence/x/JQstEw>, which proposes extending > Consumer#close with an option to leave the consumer group or not. > > Please take a look and let me know what you think, and I would appreciate > any suggestions and feedback. > > Best regards, > TengYao
