[
https://issues.apache.org/jira/browse/HBASE-4769?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13148081#comment-13148081
]
stack commented on HBASE-4769:
------------------------------
+1 on patch (Fix 'itseft' on commit).
Outside of this patch do we need to fix our 'abort'? Seems odd that we have
'abort' and then this more radical 'abort', here its called 'forceAbort', where
we call halt (Maybe we should have a 'halt' method? This patch would use it
and I believe there is another halt call over in the distributed code?).
> Abort RegionServer Immediately on OOME
> --------------------------------------
>
> Key: HBASE-4769
> URL: https://issues.apache.org/jira/browse/HBASE-4769
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.94.0
> Reporter: Nicolas Spiegelberg
> Assignee: Nicolas Spiegelberg
> Attachments: HBASE-4769.patch
>
>
> Currently, when the HRegionServer runs out of the memory, it will call
> master, which will cause more heap allocations and throw a second exception
> that it's run out of memory again. The easiest & safest way to avoid this
> OOME storm is to abort the RegionServer immediately when it hits the memory
> boundary. Part of the 89-fb to trunk port.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
