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 2019/09/25 05:13:35 UTC

[GitHub] [pulsar] volfco opened a new issue #5274: geo replicated subscribers

volfco opened a new issue #5274: geo replicated subscribers
URL: https://github.com/apache/pulsar/issues/5274
 
 
   One of the big things missing in my book, is a way to have multiple subscribers across datacenters consume messages "exactly" once. 
   
   DC A produces 5 messages. DC A has a consume subscription named TEST. DC B has a consumer with the same name. Ideally, a consumer in DC A process messages 1,2,3 while DC B is able to process 4 and 5.
   
   From my admittedly limited research, I don't think this is currently supported. Subscribers cursor is currently per DC, which allows for consumers in each DC to consume the same message.
   
   I could implement this on the client side by using the configuration store zookeeper to record a "lock" on a message ID to disallow consumption on other consumers- but this seems like something that could be implemented inside the broker and configurable on a per-namespace level. 
   
   At the expense of consumption latency and zookeeper I/O, I think this would be an amazing feature.

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