[
https://issues.apache.org/jira/browse/KAFKA-15950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jun Rao updated KAFKA-15950:
----------------------------
Summary: Serialize broker heartbeat requests (was: CommunicationEvent
should be scheduled with EarliestDeadlineFunction)
> Serialize broker heartbeat requests
> -----------------------------------
>
> Key: KAFKA-15950
> URL: https://issues.apache.org/jira/browse/KAFKA-15950
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 3.7.0
> Reporter: Jun Rao
> Assignee: Igor Soarez
> Priority: Major
>
> Currently, CommunicationEvent is scheduled with DeadlineFunction, which
> ignores the schedule time for an existing event. This wasn't an issue when
> CommunicationEvent is always periodic. However, with KAFKA-15360, a
> CommunicationEvent could be scheduled immediately for offline dirs. If a
> periodic CommunicationEvent is scheduled after the immediate
> CommunicationEvent in KafkaEventQueue, the former will cancel the latter, but
> leaves the schedule time to be periodic. This will unnecessarily delay the
> communication of the failed dir to the controller.
>
> Using EarliestDeadlineFunction will fix this issue.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
