[
https://issues.apache.org/jira/browse/KAFKA-19294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Colin McCabe resolved KAFKA-19294.
----------------------------------
Resolution: Fixed
> Fix BrokerLifecycleManager RPC timeouts
> ---------------------------------------
>
> Key: KAFKA-19294
> URL: https://issues.apache.org/jira/browse/KAFKA-19294
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 3.2.3, 3.3.2, 3.4.1, 3.5.2, 3.6.2, 3.7.2, 3.8.1, 3.9.0,
> 4.0.0
> Reporter: Colin McCabe
> Assignee: Colin McCabe
> Priority: Critical
> Fix For: 3.8.2, 3.9.1, 4.0.1, 4.1.0
>
>
> Previously, we could wait for up to half of the broker session timeout for an
> RPC to complete, and then delay by up to half of the broker session timeout.
> When taken together, these two delays could lead to brokers erroneously
> missing heartbeats.
> This change removes exponential backoff for heartbeats sent from the broker
> to the controller. The load caused by heartbeats is not heavy, and
> controllers can easily time out heartbeats when the queue length is too long.
> Additionally, we now set the maximum RPC time to the length of the broker
> period. This minimizes the impact of heavy load.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
