[
https://issues.apache.org/jira/browse/BOOKKEEPER-625?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13683101#comment-13683101
]
Uma Maheswara Rao G commented on BOOKKEEPER-625:
------------------------------------------------
This can happen in any thread. Handling OOM in all threads and shutting down
may not be a correct option I guess.
one option is : -XX:OnOutOfMemoryError="kill -9 %p" which will shutdown the
process automatically on getting OOME. But this is not graceful as we pass
'kill -9'
We can discuss more if we think we must go gracefully only. or using
UncaughtExceptionHandler can do gracefully? (but I did not use
UncaughtExceptionHandler in my past experience)
Thoughts?
> On OutOfMemoryError in NIOServerFactory thread bookie should shutdown
> ---------------------------------------------------------------------
>
> Key: BOOKKEEPER-625
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-625
> Project: Bookkeeper
> Issue Type: Bug
> Components: bookkeeper-server
> Affects Versions: 4.2.1, 4.3.0
> Reporter: Vinay
> Assignee: Vinay
> Fix For: 4.2.2, 4.3.0
>
>
> Observed OutOfMemoryError in NIOServerFactory, but it didnt bring down the
> bookie and it continued to run without serving.
> On OOME in any thread, bookie should shutdown.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
