You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (JIRA)" <ji...@apache.org> on 2013/10/17 22:40:48 UTC
[jira] [Updated] (BIGTOP-979) Add hprof dump settings on OOM to all
JVMs started by bigtop scripts
[ https://issues.apache.org/jira/browse/BIGTOP-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-979:
------------------------------------
Fix Version/s: (was: 0.7.0)
0.8.0
> Add hprof dump settings on OOM to all JVMs started by bigtop scripts
> --------------------------------------------------------------------
>
> Key: BIGTOP-979
> URL: https://issues.apache.org/jira/browse/BIGTOP-979
> Project: Bigtop
> Issue Type: Bug
> Components: Init scripts
> Reporter: Alejandro Abdelnur
> Assignee: Roman Shaposhnik
> Priority: Blocker
> Fix For: 0.8.0
>
>
> Run into the following while doing some troubleshooting:
> ------
> If you run your application with the VM flag -XX:+HeapDumpOnOutOfMemoryError a heap dump is written on the first Out Of Memory Error. There is no overhead involved unless a OOM actually occurs. This flag is a must for production systems as it is often the only way to further analyze the problem.
> ------
> IMO, it would be good if we get all startup scripts add this option to the java calls.
--
This message was sent by Atlassian JIRA
(v6.1#6144)