[
https://issues.apache.org/jira/browse/KAFKA-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17811703#comment-17811703
]
Phuc Hong Tran commented on KAFKA-16190:
----------------------------------------
also the builder is already checking which fields has changed since last
heartbeat request, my assumption is that it wouldn't send the same fields when
rejoining.
> 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
> Fix For: 3.8.0
>
>
> 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)
