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/12/09 07:28:15 UTC

[GitHub] [pulsar] wangjialing218 commented on pull request #13204: support limit message size produced by protocol handlers by maxMessag…

wangjialing218 commented on pull request #13204:
URL: https://github.com/apache/pulsar/pull/13204#issuecomment-989585480


   There could have a case when we have both pulsar and kafka producer send msgs:
   1.  `totalPendingBytes` exceed `maxMessagePublishBufferSizeInMB` and pulsar broker and KoP both stop read from producer.
   2.  Pulsar have completed all it's pending msgs, but `totalPendingBytes` still exceed `resumeThresholdPendingBytes` since KoP may hold lots of pending buffer, pulsar will not start to read from pulsar producer.
   3.  KoP completed some pending msgs and `totalPendingBytes` become lower than `resumeThresholdPendingBytes`, KoP will start to read from kafka producer. But pulsar broker may still not start to read from pulsar producer because `completedSendOperation` will never called since all pulsar msgs are sent completed.
   
   Could you please consider how to avoid this happen


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