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

Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2021/04/29 01:36:33 UTC

[GitHub] [pulsar] LiPengze97 commented on issue #10406: Message loss in non-persistent geo-replication at high sending throughput

LiPengze97 commented on issue #10406:
URL: https://github.com/apache/pulsar/issues/10406#issuecomment-828886188


   Taking a deep view into the source code, in[ NonPersistentReplicator.java](https://github.com/apache/pulsar/blob/6704f12104219611164aa2bb5bbdfc929613f1bf/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/nonpersistent/NonPersistentReplicator.java#L123), if the netty connection is not writable, the non-persistent messages are just dropped silently. I think the connection is not writable when the load is too heavy for it, am I right?
   Is 'dropping the non-persistent messages' the common design for the non-persistent topics in the pub-sub system when the load on the connection is heavy?


-- 
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.

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