You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@pulsar.apache.org by "codelipenghui (via GitHub)" <gi...@apache.org> on 2023/04/19 03:16:24 UTC

[GitHub] [pulsar] codelipenghui commented on pull request #20128: [fix] [broker] fix messages lost in scenario geo-replication if enabled duplication

codelipenghui commented on PR #20128:
URL: https://github.com/apache/pulsar/pull/20128#issuecomment-1514075304

   > send messages [1,2,3] to the remote cluster, but something is wrong. Replicator trigger rewind and try to send again.
   
   What kind of exceptions will happen to the producer? IMO, we should use infinite publish timeout, if the exception is not publish timeout, it should not be a retriable exception. We should stop the replication.


-- 
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: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org