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 2022/08/12 07:35:55 UTC

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

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

   @codelipenghui hi，I am also verifying the same scenario. If one of the three bookies has a large network delay or a slow response, the direct memory will rise and finally OOM will occur. A large number of memory leaks are found through `io.netty.leakDetectionLevel`. Adding back pressure will delay the time when OOM occurs, but it cannot fundamentally solve the problem. Is there a specific reason for this issue? Is there a solution?


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