2019-09-14 15:55:24 UTC - Matteo Merli: Growing pulsar brokers/bookies is not an issue. What is a bit more tricky is growing zk from 1 to 3 nodes. You could check that with ZK reconfiguration (from zk 3.5) or making sure to stop true quorum, copy the data to the new node and change the configuration ---- 2019-09-14 17:14:54 UTC - Joe Francis: This should not be. A message is not dispatched to a consumer until acked by the ack quorum. If that is not the case it is a bug. ---- 2019-09-14 17:17:39 UTC - Joe Francis: However I would highly doubt that is the case.. if this is being seen, it is because some config options were changed ---- 2019-09-14 17:43:13 UTC - Fredrick P Eisele: I am not finding a description of the semantics of multiple subscriptions on the same topic. I am finding good descriptions of multiple consumers on a single subscription. What are the semantics of named subscriptions? ---- 2019-09-14 17:52:45 UTC - Matteo Merli: Each subscription is independent from the others. The data is shared across all of them ---- 2019-09-14 20:59:24 UTC - Fredrick P Eisele: So, given two subscriptions, S & R, to a topic T with corresponding consumers, S1 S2 S3 R1 R2, and messages, T1 T2 T3. Suppose S1 acknowledges T1; does R1 also receive T1? ---- 2019-09-14 21:01:47 UTC - Fredrick P Eisele: If S1 acknowledges T1 before R1 is created; does R1 also receive T1? ---- 2019-09-14 21:04:13 UTC - Fredrick P Eisele: How does changing the retention policy for T change the result? (I believe T1 could be deleted before R is created.) heart : Poule, Cory Davenport ---- 2019-09-14 23:58:18 UTC - Cory Davenport: From everything I've been testing thus far. It seems to be the case that each subscription to a topic will receive the message if it is created before the message creation. If the subscription is created after the message was created it will not get the message.
Only from my own test thus far. Trying to figure out as well if there is a way to get new subscriptions to receive message created before the subscription creation time. Either acked messages or even the un-acked messaged. heart : Poule ---- 2019-09-15 00:18:39 UTC - Matteo Merli: Take a look at ConsumerBuilder.subscriptionInitialPosition() <https://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#subscriptionInitialPosition-org.apache.pulsar.client.api.SubscriptionInitialPosition-> ---- 2019-09-15 00:19:18 UTC - Matteo Merli: Yes ---- 2019-09-15 00:21:02 UTC - Matteo Merli: Not by default. Subscriptions are created by default at the end of the topic. Take a look at <https://pulsar.apache.org/api/client/org/apache/pulsar/client/api/ConsumerBuilder.html#subscriptionInitialPosition-org.apache.pulsar.client.api.SubscriptionInitialPosition-> for subscribing at the beginning of the topic ---- 2019-09-15 00:22:53 UTC - Matteo Merli: As mentioned above, you first need to specify to create the subscription at the beginning of the topic. The retention parameters can be used to determined which data is retained when either there are no subscriptions or all the subscriptions have acked the messages ---- 2019-09-15 00:52:46 UTC - Poule: is Earliest for acked or non-acked ---- 2019-09-15 05:29:41 UTC - Xiaolei Zhu: @Xiaolei Zhu has joined the channel ----
