pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [pulsar-client-go] keithnull commented on issue #177: Not support multi pulsar cluster addresses
Date Fri, 22 May 2020 03:27:06 GMT

keithnull commented on issue #177:
URL: https://github.com/apache/pulsar-client-go/issues/177#issuecomment-632457978


   @wolfstudy 
   
   Hi, I'm interested in this issue (for OSPP Summer 2020) and willing to work on it. But
I can't fully understand why multi pulsar cluster addresses are needed for a client.
   
   In Pulsar's [doc](https://pulsar.apache.org/docs/en/concepts-architecture-overview/#service-discovery),
service discovery section, I find that 
   
   > Clients connecting to Pulsar brokers need to be able to communicate with an entire
Pulsar instance using a single URL.
   
   So why do we need multi cluster addresses in the client?
   


----------------------------------------------------------------
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



Mime
View raw message