[
https://issues.apache.org/jira/browse/KAFKA-19047?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mickael Maison updated KAFKA-19047:
-----------------------------------
Fix Version/s: (was: 4.0.1)
> Broker registrations are slow if previously fenced or shutdown
> --------------------------------------------------------------
>
> Key: KAFKA-19047
> URL: https://issues.apache.org/jira/browse/KAFKA-19047
> Project: Kafka
> Issue Type: Bug
> Components: controller
> Affects Versions: 4.0.0
> Reporter: Alyssa Huang
> Assignee: Alyssa Huang
> Priority: Major
> Fix For: 4.1.0
>
>
> BrokerLifecycleManager prevents registration of a broker w/ an id it has seen
> before with a different incarnation id if the broker session expires. On
> clean shutdown and restart of a broker this can cause an unnecessary delay in
> re-registration while the quorum controller waits for the session to expire.
> ```
> [BrokerLifecycleManager id=1] Unable to register broker 1 because the
> controller returned error DUPLICATE_BROKER_REGISTRATION
> ```
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
