lucasbru opened a new pull request, #23978: URL: https://github.com/apache/kafka/pull/23978
KIP-1071 defines STREAMS_INVALID_TOPOLOGY_EPOCH for a member that sends a topology that differs from the group's topology at the same epoch, but the group coordinator returned INVALID_REQUEST in that case. The streams group heartbeat now returns STREAMS_INVALID_TOPOLOGY_EPOCH when the topology differs at the same epoch. When the topology differs at a higher epoch, it keeps returning INVALID_REQUEST, since topology updates are not supported. The KIP-1331 topology description push also returns STREAMS_INVALID_TOPOLOGY_EPOCH instead of INVALID_REQUEST when the pushed epoch does not match the group's current topology epoch, and StreamsGroupTopologyDescriptionUpdateResponse lists it as a supported error. The client handles it as before, dropping the push without retrying, but logs it at info level, since the epoch can change between the heartbeat that requested the push and the push itself. Clients already treat STREAMS_INVALID_TOPOLOGY_EPOCH on the heartbeat as fatal, the same as INVALID_REQUEST, so client behavior does not change. -- 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]
