hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nicolas Spiegelberg (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3603) Remove -XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
Date Tue, 08 Nov 2011 19:35:52 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146495#comment-13146495

Nicolas Spiegelberg commented on HBASE-3603:

We're one of those wierdos, can we add this feature back in, but comment it out?  I think
it's good to have a recommended list of optional features to play with and then explain why
they're disabled for the common use case.
> Remove  -XX:+HeapDumpOnOutOfMemoryError  autodump of heap option on OOME
> ------------------------------------------------------------------------
>                 Key: HBASE-3603
>                 URL: https://issues.apache.org/jira/browse/HBASE-3603
>             Project: HBase
>          Issue Type: Task
>            Reporter: stack
>            Assignee: stack
>            Priority: Minor
> By default the  -XX:+HeapDumpOnOutOfMemoryError  option is set for HBase.  Means we'll
dump heap when we OOME.  In the heaps we run with 8G, 16G, etc., these can make for hefty
files.  No one really looks at these things other than a few weirdos and even then, the interesting
ones are too big to ship easily.  Meantime, they can cause headache.  E.g. you are on EC2,
root is but a small partition, and you set up hbase on root partition... a heap dump could
cause your root partition to fill and make the machine unapproachable.

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


View raw message