lhotari commented on issue #23889: URL: https://github.com/apache/pulsar/issues/23889#issuecomment-2612203304
> However, if the broker is forced to exit due to issues like hardware failure, network problems, or being terminated with `kill -9`, it does not call the unregister method to delete its metadata. This results in the metadata for brokers that are no longer accessible remaining in the system. The metadata should get deleted automatically when the session expires. When a broker crashes, a new broker instance would not be able to start until the session expires and the empheral metadata entries expire. There's `EnumSet.of(CreateOption.Ephemeral)`: https://github.com/apache/pulsar/blob/66d1bb0d734f12d758b0f0e9e3c0b42543508f8d/pulsar-broker/src/main/java/org/apache/pulsar/broker/loadbalance/extensions/BrokerRegistryImpl.java#L142 What metadata store implementation are you using? (What version, deployment type?) Just in case you are using Oxia since you are facing this issue. With Oxia there was a related bug, addressed by https://github.com/streamnative/oxia/pull/534 since Oxia v0.10.0. With Oxia, I believe it's worth tracking the [recent releases](https://github.com/streamnative/oxia/releases) and keeping up-to-date. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
