[
https://issues.apache.org/jira/browse/KAFKA-19288?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17954114#comment-17954114
]
Lucas Brutschy commented on KAFKA-19288:
----------------------------------------
https://github.com/apache/kafka/pull/19818
> Ensure new consumer joining attempt not overwritten on delayed HB response to
> previous leave
> --------------------------------------------------------------------------------------------
>
> Key: KAFKA-19288
> URL: https://issues.apache.org/jira/browse/KAFKA-19288
> Project: Kafka
> Issue Type: Bug
> Components: clients, consumer
> Reporter: Lianet Magrans
> Assignee: Lucas Brutschy
> Priority: Major
> Labels: kip-848-client-support
> Fix For: 4.1.0
>
>
> For the asyn consumer, check and cover edge case where the consumer may
> transition to JOINING, but receive a delayed response to a previous leave
> request. We should ensure that the response is ignored and the consumer joins
> as it intended.
> I expect this doesn't usually happens given that the unsubscribe is a
> blocking operation, so the consumer won't be able to join until the
> unsubscribe completes. But if the leave request doesn't get a response in
> time (unsubscribes fails quietly), and the response arrives after it, I
> expect the joining could be overwritten (member updating it's joining epoch 0
> to the -1 epoch received in the response)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
