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

Posted to issues@bookkeeper.apache.org by GitBox <gi...@apache.org> on 2021/06/08 11:36:10 UTC

[GitHub] [bookkeeper] lhotari commented on issue #2729: 【BUG】BookKeeper Netty chennel OOM

lhotari commented on issue #2729:
URL: https://github.com/apache/bookkeeper/issues/2729#issuecomment-856687753


   @hangc0276 Do you have a chance to run with `-Dio.netty.leakDetectionLevel=advanced -Dio.netty.leakDetection.targetRecords=30` in the JVM options for the BookKeeper server? That would enable the Netty leak detector and print out log entries that would help locate the possible leak.
   
   It's also possible that there isn't a memory leak and it's simply caused by high memory requirements when there's high load. When using Pulsar, the default configuration for BookKeeper doesn't enable the specific backpressure features that are available in Bookkeeper server (#1409) and client (#1086). There's a separate enhancement request in Pulsar to make use of these features. It is filed as https://github.com/apache/pulsar/issues/10439 . 
   


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