You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/08/04 01:56:21 UTC

[GitHub] [pulsar] wangjialing218 opened a new issue #7736: Broker did not return correct url when client specify advertisedListenerName

wangjialing218 opened a new issue #7736:
URL: https://github.com/apache/pulsar/issues/7736


   **Describe the bug**
   When client lookup the broker url for a new created topics (no one owns the bundle of the topic) with advertisedListenerName, the searchForCandidateBroker() function return the default advertiesed url instead of the url specified by advertisedListenerName if the candidateBroker is not self.
   
   **To Reproduce**
   1. Start broker with advertisedListeners setting, make sure the client can only connect to broker through the url specified by the advertisedListener.
   2. Create a topic with 50 partitions and  use client to produce messages with correct advertisedListenerName.
   3. For some partition topics, client got the default advertiesed url and failed to connect to broker.
   
   **Expected behavior**
   Client should get the correct url by the specified advertisedListenerName.
   


----------------------------------------------------------------
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:
users@infra.apache.org



[GitHub] [pulsar] wolfstudy closed issue #7736: Broker did not return correct url when client specify advertisedListenerName

Posted by GitBox <gi...@apache.org>.
wolfstudy closed issue #7736:
URL: https://github.com/apache/pulsar/issues/7736


   


----------------------------------------------------------------
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:
users@infra.apache.org