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/04/08 09:09:47 UTC

[GitHub] [pulsar] kitekite2020 commented on issue #6693: We would like to have pulsar clusters in two data centers. They active and active. And we would like to replicate messages from one site and the other. i.e. the subscriber from each site will receive messages from publishers at two sites. And no message loss.

kitekite2020 commented on issue #6693: We would like to have pulsar clusters in two data centers. They active and active. And we would like to replicate messages from one site and the other. i.e. the subscriber from each site will receive messages from publishers at two sites. And no message loss.  
URL: https://github.com/apache/pulsar/issues/6693#issuecomment-610844869
 
 
   We would like to have pulsar clusters in two data centers. They are active and active. And we would like to replicate messages from one site to the other. i.e. the subscriber from one site will receive messages from publishers at two sites. And no message loss. If one site is down, the other site can continue to work. 
   We are thinking of geo replication. But since geo replication is asynchronous, we are worried about message loss. Every single message cannot be lost.  
   Then we are thinking to have synchronous replication, at bookkeeper level, cross two sites. First difficulty is there is no examples of how to do it without global zookeeper. If we use two clusters to manage each site, we need a global configuration store to manage two sites information which becomes a single point failure. If we use global zookeeper, one zookeeper for two sites, due to zookeeper cluster has to be 2*n+1 nodes, it means if the site with n+1 node fails, the other site also stops working.
   Is my understanding right? Is there a possible solution with Pulsar for us? Thanks.   

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


With regards,
Apache Git Services