[
https://issues.apache.org/jira/browse/KAFKA-13755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Arthur updated KAFKA-13755:
---------------------------------
Description:
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.
was:
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 other events, we may not
process the heartbeat before the broker attempts to send another one.
> 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: David Arthur
> Priority: Minor
> Labels: kip-500
> Fix For: 3.2.0
>
>
> 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.1#820001)
