hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (HBASE-3603) Remove -XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
Date Fri, 04 Mar 2011 18:25:36 GMT

     [ https://issues.apache.org/jira/browse/HBASE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

stack resolved HBASE-3603.
--------------------------

      Resolution: Fixed
        Assignee: stack
    Hadoop Flags: [Reviewed]

Removed in TRUNK.

> 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.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message