lhotari commented on issue #10054: URL: https://github.com/apache/pulsar/issues/10054#issuecomment-2022596681
> Hey, was there any update on this ? I'm using pulsar 2.10.x , and facing the same issue. I read through the related issues on this repo, but even with continuous message production (100 messages with 1 sec sleep between each, as well as 1000 messages with 0.1 sleep between each) and dedup enabled. I'm not getting the expected behavior of consuming x messages on one cluster, closing the client, and starting from x+1 st message on second cluster (or anywhere near x for that matter, the second consumer always start from 0th message). set the snapshot timeout to 60, but not sure where to see if the snapshot is failing, there are no obvious logs related to replication failure in broker. @YJDoc2 there are discussions https://github.com/apache/pulsar/discussions/22315 and https://github.com/apache/pulsar/discussions/21612 which might contain some useful information. Since replicated subscriptions will only replicate the mark-delete position, it is worth checking `pulsar-admin topics stats-internal` for the topic in each cluster to check the subscription state. -- 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]
