chickenchickenlove commented on PR #23768: URL: https://github.com/apache/kafka/pull/23768#issuecomment-6123476798
Thanks, @lucasbru ! I agree that resending additional member metadata after a heartbeat failure would bring the behavior closer to the consumer group protocol. Would it make sense to keep topology restricted to join requests, as required by the current protocol? We could discuss adding topology handling to the retry path separately when considering topology evolution. The current coordinator-side fix already addresses the issue for existing clients. Would you prefer to include the additional client-side improvement in KAFKA-21255, or track it in a separate ticket? What do you think? -- 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]
