[jira] [Resolved] (KAFKA-14392) KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms

["Ron Dagostino (Jira)" <ji...@apache.org>]

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

Ron Dagostino resolved KAFKA-14392.
-----------------------------------
    Fix Version/s: 3.5.0
       Resolution: Fixed

> KRaft broker heartbeat timeout should not exceed broker.session.timeout.ms
> --------------------------------------------------------------------------
>
>                 Key: KAFKA-14392
>                 URL: https://issues.apache.org/jira/browse/KAFKA-14392
>             Project: Kafka
>          Issue Type: Improvement
>          Components: kraft
>    Affects Versions: 3.3.0, 3.4.0, 3.3.1, 3.3.2
>            Reporter: Ron Dagostino
>            Assignee: Ron Dagostino
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> KRaft brokers maintain their liveness in the cluster by sending BROKER_HEARTBEAT requests to the active controller; the active controller fences a broker if it doesn't receive a heartbeat request from that broker within the period defined by `broker.session.timeout.ms`.  The broker should use a request timeout for its BROKER_HEARTBEAT requests that is not larger than the session timeout being used by the controller; doing so creates the possibility that upon controller failover the broker might not cancel an existing heartbeat request in time and then subsequently heartbeat to the new controller to maintain an uninterrupted session in the cluster.  In other words, a failure of the active controller could result in under-replicated (or under-min ISR) partitions simply due to a delay in brokers heartbeating to the new controller.



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