[
https://issues.apache.org/jira/browse/HADOOP-6279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Todd Lipcon updated HADOOP-6279:
--------------------------------
Status: Patch Available (was: Open)
Does not include unit tests - this is an existing open issue HADOOP-3634. This
patch is a one-liner, though.
Manual verification steps:
1) Launch daemon with NoEmitMetricsContext configured in
hadoop-metrics.properties
2) Go to /metrics on web UI
3) Verify totalMemoryM is present
> 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
> 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.
