You are viewing a plain text version of this content. The canonical link for it is here.

Posted to jira@kafka.apache.org by "Alyssa Huang (Jira)" <ji...@apache.org> on 2025/03/27 02:34:00 UTC

[jira] [Created] (KAFKA-19047) Broker registrations are slow if previously fenced or shutdown

Alyssa Huang created KAFKA-19047:
------------------------------------

             Summary: 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: Improvement
            Reporter: Alyssa Huang


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)