meleagle commented on issue #7470: URL: https://github.com/apache/pulsar/issues/7470#issuecomment-677751653
Hello @zymap, The logs weren't helpful for me to look at as there was no errors but I can give an example of the properties I set to get to the issue. In broker.conf I would clear out the brokerServicePort and AdvertisedAddress fields. Then I would set the advertisedListeners and internalListenerName to something like below (with valid ip addressess in the real case). advertisedListeners=internal:pulsar://0.0.0.0:6650,external:pulsar://1.1.1.1:6660 internalListenerName=internal So when I would start pulsar up normally with just just using the advertisedAddress and the brokerServicePort I would see a line like below in the logs where the broker url was the combination of the two which is what I expected. ``` 15:46:33.806 [main] INFO org.apache.pulsar.broker.PulsarService - messaging service is ready, bootstrap service port = 8080, broker url= pulsar://0.0.0.0:6650 ``` But when I used the advertisedListeners and internalListenerName fields, instead of the broker url being the ip:port combination that is expected from the advertisedListeners list it was getting resolved to the instances hostname instead. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
