[
https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Bowen updated HADOOP-1562:
--------------------------------
Attachment: 1562_3.patch
Fixed a problem arising from the fact that classes which are normally in
separate executables can be combined in a single executable. Only one class can
"name" the process so far as the JVM metrics is concerned, so it now just takes
the first one. Any subsequent attempts to initiate JVM metrics reporting will
just cause a message to be logged (whereas in the previous patch, a
RuntimeException was thrown).
> Report Java VM metrics
> ----------------------
>
> Key: HADOOP-1562
> URL: https://issues.apache.org/jira/browse/HADOOP-1562
> Project: Hadoop
> Issue Type: New Feature
> Components: metrics
> Reporter: David Bowen
> Assignee: David Bowen
> Attachments: 1562.patch, 1562_1.patch, 1562_2.patch, 1562_3.patch
>
>
> It would be useful to have each Java process in Hadoop (JobTracker,
> TaskTracker, NameNode and DataNode) report some Java VM metrics. E.g.
> heap/non-heap memory used/committed, number of garbage collections and
> percentage of time spent in GC, number of threads that are
> runnable/blocked/waiting/etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
