[
https://issues.apache.org/jira/browse/HADOOP-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12763972#action_12763972
]
Hudson commented on HADOOP-6279:
--------------------------------
Integrated in Hadoop-Common-trunk #122 (See
[http://hudson.zones.apache.org/hudson/job/Hadoop-Common-trunk/122/])
. Add Runtime::maxMemory to JVM metrics. Contributed by Todd Lipcon
> Add JVM memory usage to JvmMetrics
> ----------------------------------
>
> Key: HADOOP-6279
> URL: https://issues.apache.org/jira/browse/HADOOP-6279
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 0.20.2, 0.21.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Minor
> Fix For: 0.22.0
>
> Attachments: hadoop-6279.txt
>
>
> The JvmMetrics currently publish memory usage from the MemoryMXBean. This is
> useful, but doesn't include the total heap size (eg as displayed in the JT
> Web UI).
> It would be nice to expose Runtime.getRuntime().maxMemory() as part of
> JvmMetrics.
> It seems that Runtime.getRuntime().totalMemory() (used by the JT for "memory
> used") is the same as the 'memHeapCommittedM' which already exists.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
