YJDoc2 commented on issue #10054: URL: https://github.com/apache/pulsar/issues/10054#issuecomment-2029510602
Hey @lhotari , thanks for the resources, they helped a lot. So to be clear, from what I have understood, is the following correct : For two clusters A and B, where cluster B is replicating cluster A (so cluster A is the "main" one) - When subscription state replication is NOT enabled, the messages will be replicated from A -> B, and the connected consumers in both clusters, irrespective of their type (exclusive or shared) will consume all the message from the point of enabling the replication, and act as if they are connected to two independent clusters. - When subscription state replication IS enabled, only the delete marker is replicated. So even if one consumer consumes and acknowledges a message in one cluster (say A), another consumer (of same subscription) in the other cluster (B) does not get any notification / information of this. When the pulsar (in A or B) decides that some of the messages in queue should be deleted (by either ttl or storage reasons or some internal algo) , that info _is_ shared across clusters, and now newly attached consumers in both the cluster can consumer messages only from the new deletion point onward and not before. Is my understanding correct? 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
