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 16:35:51 UTC

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

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


   @hangc0276 It is more than likely that there is no leak at all and application simply runs out of (direct) memory under specific load (when auditor/autorecovery works).
   
   I think your options are:
   
   1.  increase direct memory (jvm option)
   2. set `autoRecoveryDaemonEnabled=false` on bookies and[ run autorecovery as a separate instance(s)](https://bookkeeper.apache.org/docs/latest/admin/autorecovery/) - I think this is the best option in general; autorecovery won't interfere with bookie.
   3. figure out the way to throttle the autorecovery (I don't remember off the top of my head what's going on there/which config params could help) - this can be helpful for option 2 as well
   


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