[jira] [Resolved] (KAFKA-17293) New consumer HeartbeatRequestManager should rediscover disconnected coordinator

["Lianet Magrans (Jira)" <ji...@apache.org>]

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

Lianet Magrans resolved KAFKA-17293.
------------------------------------
      Reviewer: Lianet Magrans
    Resolution: Fixed

> New consumer HeartbeatRequestManager should rediscover disconnected coordinator
> -------------------------------------------------------------------------------
>
>                 Key: KAFKA-17293
>                 URL: https://issues.apache.org/jira/browse/KAFKA-17293
>             Project: Kafka
>          Issue Type: Bug
>          Components: clients, consumer
>    Affects Versions: 3.7.0, 3.8.0, 3.7.1
>            Reporter: Lianet Magrans
>            Assignee: TengYao Chi
>            Priority: Blocker
>              Labels: kip-848-client-support
>             Fix For: 4.0.0
>
>
> The HeartbeatRequestManager attempts to send heartbeat requests to the coordinator. In the case that it gets a DisconnectException, it simply retries the request with backoff ([here|https://github.com/apache/kafka/blob/837684a1b9b3bad244613211e90b67cf9170fb44/clients/src/main/java/org/apache/kafka/clients/consumer/internals/HeartbeatRequestManager.java#L323]), but it should rediscover the coordinator first (by calling "markCoordinatorUnknown") to ensure it sends the HBs to the right coordinator. 
> Note that this disconnection case are properly handled in the CommitRequestManager ([here|https://github.com/apache/kafka/blob/837684a1b9b3bad244613211e90b67cf9170fb44/clients/src/main/java/org/apache/kafka/clients/consumer/internals/CommitRequestManager.java#L886]) but are missing in the HeartbeatRequestManager.



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