You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2011/03/04 07:30:37 UTC
[jira] Created: (HBASE-3603) Remove
-XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
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
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
[jira] Commented: (HBASE-3603) Remove
-XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13003607#comment-13003607 ]
Hudson commented on HBASE-3603:
-------------------------------
Integrated in HBase-TRUNK #1771 (See [https://hudson.apache.org/hudson/job/HBase-TRUNK/1771/])
> 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
[jira] Commented: (HBASE-3603) Remove
-XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
Posted by "Todd Lipcon (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002660#comment-13002660 ]
Todd Lipcon commented on HBASE-3603:
------------------------------------
yea, I agree
> 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
> 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
[jira] Resolved: (HBASE-3603) Remove
-XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
Posted by "stack (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (HBASE-3603) Remove
-XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
Posted by "Nicolas Spiegelberg (Commented) (JIRA)" <ji...@apache.org>.
[ 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
[jira] Commented: (HBASE-3603) Remove
-XX:+HeapDumpOnOutOfMemoryError autodump of heap option on OOME
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-3603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13002897#comment-13002897 ]
Andrew Purtell commented on HBASE-3603:
---------------------------------------
Committed to 0.90 branch also.
> 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