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

Posted to notifications@accumulo.apache.org by GitBox <gi...@apache.org> on 2021/07/02 12:14:55 UTC

[GitHub] [accumulo] milleruntime commented on pull request #2181: WIP: Update LogReader to utilize RecoveryLogsIterator

milleruntime commented on pull request #2181:
URL: https://github.com/apache/accumulo/pull/2181#issuecomment-872952860


   > > java.lang.OutOfMemoryError: Java heap space
   > > -XX:OnOutOfMemoryError="kill -9 %p"
   > > Executing /bin/sh -c "kill -9 41830"...
   > > [1]    41830 killed     accumulo wal-info
   > 
   > For the OOM issue, should I adjust heap space for wal-info inside accumulo-env.sh or is that something we should let the user decide on what heap space to give that particular utility? I tested upping the limit to 512m and did not run into the error.
   
   I think we should try and prevent the OOM error. It could be reading too much with the null range.


-- 
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: notifications-unsubscribe@accumulo.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org