[
https://issues.apache.org/jira/browse/KAFKA-16190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17818976#comment-17818976
]
Kirk True commented on KAFKA-16190:
-----------------------------------
[~phong260702] thanks for your willingness to help out on this task! :)
We're working against a tight deadline to get these blocker/critical tasks done.
Is there any other information/help you need? Due you have a sense of when
you'll have a pull request ready to review?
Thanks!
> 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: Critical
> 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 reset on failure scenarios, which
> should cover the fence+rejoin sequence).
> Note that the existing HeartbeatRequestManagerTest.testHeartbeatState misses
> this exact 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)
