[
https://issues.apache.org/jira/browse/KAFKA-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17556134#comment-17556134
]
Colin McCabe edited comment on KAFKA-13755 at 6/19/22 9:36 PM:
---------------------------------------------------------------
As of 3.3, we now use {{config.brokerHeartbeatIntervalMs}} as the deadline
It should be a good improvement for clusters under load
was (Author: cmccabe):
We now use {{config.brokerHeartbeatIntervalMs}} as the deadline
It should be a good improvement for clusters under load
> Broker heartbeat event should have deadline
> -------------------------------------------
>
> Key: KAFKA-13755
> URL: https://issues.apache.org/jira/browse/KAFKA-13755
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Reporter: David Arthur
> Assignee: Colin McCabe
> Priority: Minor
> Labels: kip-500
> Fix For: 3.3
>
>
> When we schedule the event for processing the broker heartbeat request in
> QuroumController, we do not give a deadline. This means that the event will
> only be processed after all other events which do have a deadline. In the
> case of the controller's queue getting filled up with deadline (i.e.,
> "deferred") events, we may not process the heartbeat before the broker
> attempts to send another one.
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
