pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] JevonQ edited a comment on issue #3303: [Question] A few questions on using Pulsar in different scenarios
Date Tue, 08 Jan 2019 01:50:01 GMT
JevonQ edited a comment on issue #3303: [Question] A few questions on using Pulsar in different
URL: https://github.com/apache/pulsar/issues/3303#issuecomment-452145996
   > > Yes, I want to create a multi-cluster instance without replication among themselves
and allow users to access the topic within each cluster. I cannot figure out a way to achieve
   > if it is "multi-cluster" instance without replication, then each cluster is a separate
cluster. You have to manage which topic in which cluster.
   > Alternatively, you can setup a "global" instance, which requires a "global" zookeeper
that spreads across multiple physical locations. In this way, pulsar will be acting as a "whole"
system and managing the topic assignments.
   The global zookeeper has the global view of all topic assignments, every broker will have
the view cached locally? Does that mean the pulsar client can find which broker hosts the
topic via any broker?
   BTW, for the zookeeper pulsar uses, is it the official versioned zookeeper or a modified
versioned zookeeper? I mean if we already have a zookeeper available, can we just use it as
the local zookeeper or global zookeeper for pulsar?
   > > does that mean I need to set the url address to the node ip where the pulsar
discovery process run?
   > If you want to setup additional discovery service, then the service urls are the DNS
of the discovery service nodes and you have to run several processes for fault tolerance.
   > However you don't have to do so, broker already offers discovery. If you have DNS
or load balancer for your brokers, you can just use that DNS in the service urls.

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

View raw message