You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jira@kafka.apache.org by "Lianet Magrans (Jira)" <ji...@apache.org> on 2023/10/04 14:32:00 UTC

[jira] [Updated] (KAFKA-15533) Ensure HeartbeatRequestManager only send out some fields once

     [ https://issues.apache.org/jira/browse/KAFKA-15533?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lianet Magrans updated KAFKA-15533:
-----------------------------------
        Parent: KAFKA-14048
    Issue Type: Sub-task  (was: Bug)

> Ensure HeartbeatRequestManager only send out some fields once
> -------------------------------------------------------------
>
>                 Key: KAFKA-15533
>                 URL: https://issues.apache.org/jira/browse/KAFKA-15533
>             Project: Kafka
>          Issue Type: Sub-task
>            Reporter: Philip Nee
>            Assignee: Philip Nee
>            Priority: Major
>
> We want to ensure ConsumerGroupHeartbeatRequest is as lightweight as possible, so a lot of fields in it don't need to be resend. An example would be the rebalanceTimeoutMs, currently we have the following code:
>  
>  
> {code:java}
> ConsumerGroupHeartbeatRequestData data = new ConsumerGroupHeartbeatRequestData()
>     .setGroupId(membershipManager.groupId())
>     .setMemberEpoch(membershipManager.memberEpoch())
>     .setMemberId(membershipManager.memberId())
>     .setRebalanceTimeoutMs(rebalanceTimeoutMs); {code}
>  
>  
> We should encapsulate these once-used fields into a class such as HeartbeatMetdataBuilder, and it should maintain a state of whether a certain field needs to be sent or not.
>  
> Note that, currently only 3 fields are mandatory in the request:
>  * groupId
>  * memberEpoch
>  * memberId



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