merlimat commented on a change in pull request #13230:
URL: https://github.com/apache/pulsar/pull/13230#discussion_r767069070
##########
File path: site2/docs/administration-geo.md
##########
@@ -214,4 +214,5 @@ Consumer<String> consumer =
client.newConsumer(Schema.STRING)
### Limitations
-When you enable replicated subscription, you're creating a consistent
distributed snapshot to establish an association between message ids from
different clusters. The snapshots are taken periodically. The default value is
`1 second`. It means that a consumer failing over to a different cluster can
potentially receive 1 second of duplicates. You can also configure the
frequency of the snapshot in the `broker.conf` file.
+* When you enable replicated subscription, you're creating a consistent
distributed snapshot to establish an association between message ids from
different clusters. The snapshots are taken periodically. The default value is
`1 second`. It means that a consumer failing over to a different cluster can
potentially receive 1 second of duplicates. You can also configure the
frequency of the snapshot in the `broker.conf` file.
+* Only markDeletePosition will be synced in replicated subscriptions while the
individuallyDeletedMessages won't be synced which means the acknowledges are
being done out of order cannot be synced to other clusters through replicated
subscriptions.
Review comment:
```suggestion
* Only the base line cursor position will be synced in replicated
subscriptions while the individual acknowledgments won't be synced. This that
the messages acknowledged out-of-order could end up getting delivered again, in
the case of a cluster failover.
```
--
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.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
