[GitHub] [pulsar] michaeljmarshall commented on issue #16998: Broker direct memory leak due to BKNotEnoughBookiesException

[GitBox <gi...@apache.org>]

michaeljmarshall commented on issue #16998:
URL: https://github.com/apache/pulsar/issues/16998#issuecomment-1244833965

   Do you have any updates on this OOM issue? I have been tracking similar issues recently, and I am thinking we probably need to improve Pulsar's back pressure implementation. Specifically, if the bookie cannot handle the broker's load, then the broker should provide back pressure to producers/consumers so that the broker works without running out of memory.
   
   One side effect of decreasing overall throughput in order to protect broker memory could be harder load balancing logic because the broker might not look under pressure, but in a sense, it is, and there might be other brokers that could handle higher throughput, depending on the bookkeeper topology. 


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