Meet0861 opened a new issue, #21897: URL: https://github.com/apache/pulsar/issues/21897
### Search before asking - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Version 2.10.4 ### Minimal reproduce step We are hitting a bug where a leader broker identifier becomes unresolvable when we are not setting a internalListener with a host:port (as set in advertised address) as the leader broker's identifier uses the internal listener's host name and in all other cases the advertisedAddress is used. warnings in broker logs: `05:19:57.541 [pulsar-2-5] WARN org.apache.pulsar.broker.namespace.NamespaceService - The current leader broker LeaderBroker(serviceUrl=http://xx.yy.zz.xy:8080/) isn't active. Handling load manager decisions in a decentralized way. NamespaceBundle[tenant/ns/0x2fffffff_0x3269f69d] ` Reason - `05:19:55.176 [pulsar-2-6] WARN org.apache.pulsar.broker.namespace.NamespaceService - Broker http://xx.yy.zz.xy:8080/ (xx.yy.zz.xy:8080) couldn't be found in available brokers prod-xx-1-pulsar-broker-10:8080,prod-xx-1-pulsar-broker-yy-7:8080,prod-xx-1-pulsar-broker-zz-5:8080,prod-xx-1-pulsar-broker-7:8080,prod-xx-1-pulsar-broker-zz-2:8080,prod-xx-1-pulsar-broker-yy-1:8080,prod-xx-1-pulsar-broker-yy-4:8080,prod-xx-1-pulsar-broker-2:8080,prod-xx-1-pulsar-broker-12:8080,prod-xx-1-pulsar-broker-yy-2:8080,prod-xx-1-pulsar-broker-15:8080` here it seems related to the advertised listerners/address. we are setting the advertisedAddress as a hostname of a stateful set and advertisedListeners as broker pod ips and not setting a internalListenerName from above logs, we can see that for leader broker's load manager using the (ip:port) because if we dont set the internal Listener Name it picks the first advertised listener as the internalListener Name. Configs : ``` advertisedAddress=prod-xx-pulsar-broker-0 advertisedListeners=public_pulsar:pulsar://xx.yy.zz.xy:6650,public_http:http://xx.yy.zz.xy:8080/ ``` ### What did you expect to see? Here seems some confusion with advertisedAddress and advertisedListeners, because in some cases advertisedAddress is used and in some advertisedListeners, which made it mandatory to set the advertisedAddress in advertisedListeners as well. There should be consistent ways for a unique identifier for a broker. ### What did you see instead? Disconnects from client side because of leader broker info is unresolvable ### Anything else? _No response_ ### Are you willing to submit a PR? - [ ] I'm willing to submit a PR! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
