You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Kirk True (Jira)" <ji...@apache.org> on 2024/01/27 00:33:00 UTC

[jira] [Commented] (KAFKA-16190) Member should send full heartbeat when rejoining

    [ https://issues.apache.org/jira/browse/KAFKA-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811431#comment-17811431 ] 

Kirk True commented on KAFKA-16190:
-----------------------------------

[~lianetm] is this something we want in 3.8?

> Member should send full heartbeat when rejoining
> ------------------------------------------------
>
>                 Key: KAFKA-16190
>                 URL: https://issues.apache.org/jira/browse/KAFKA-16190
>             Project: Kafka
>          Issue Type: Sub-task
>          Components: clients, consumer
>            Reporter: Lianet Magrans
>            Assignee: Quoc Phong Dang
>            Priority: Major
>              Labels: client-transitions-issues, kip-848-client-support, newbie
>
> The heartbeat request builder should make sure that all fields are sent in the heartbeat request when the consumer rejoins (currently the HeartbeatRequestManager request builder is only reset on failure scenarios). 
> This should fix the issue that a client that is subscribed to a topic and gets fenced, should try to rejoin providing the same subscription it had. 
> Note that the existing HeartbeatRequestManagerTest.testHeartbeatState misses this case given that it does explicitly change the subscription when it gets fenced. We should ensure we test a consumer that keeps it same initial subscription when it rejoins after being fenced.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)