2018-11-14 09:59:42 UTC - Christophe Bornet: > From client side, you could publish timestamps of last message acknowledged in a different topic. Then use that at failover time to set reposition the subscription in the 2nd DC to a particular time. It’s not “difficult” but it’s not automated either.. . That would work for cumulative ack, but not for selective ack, isnt' it ? ---- 2018-11-14 12:45:02 UTC - wangruihuan: @wangruihuan has joined the channel ---- 2018-11-14 16:39:22 UTC - AB: @AB has joined the channel ---- 2018-11-14 17:19:59 UTC - Nicolas Ha: how is the `subscriptionName` used in pulsar? What purpose does it serve? ---- 2018-11-14 17:21:08 UTC - Ivan Kelly: it depends on whether you use exclusive, failover or shared ---- 2018-11-14 17:21:37 UTC - Ivan Kelly: for exclusive, the cursor is tied to the name, so if you disconnect and reconnect with the same name, you'll pick up where you left off ---- 2018-11-14 17:21:53 UTC - Ivan Kelly: for failover, only one consumer with a specific name will get data ---- 2018-11-14 17:22:29 UTC - Ivan Kelly: for shared, the messages are shared among all the consumers with the same subscription name ---- 2018-11-14 17:41:00 UTC - Nicolas Ha: oh - pretty important then :smile: any place I can read more? specifically about “shared”? ---- 2018-11-14 17:43:00 UTC - Grant Wu: <https://pulsar.apache.org/docs/en/concepts-messaging/#subscription-modes> +1 : Matteo Merli, Nicolas Ha, Ali Ahmed, jia zhai ----
