[
https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510220
]
Devaraj Das edited comment on HADOOP-1562 at 7/4/07 9:11 AM:
-------------------------------------------------------------
Code looks good. I have one comment - the way the objects of type JvmMetrics
are created is different in the NameNode/DataNode from the way they are created
in JobTracker/TaskTracker. I think it is better to have it uniform, i.e., pass
sessionId even to the NameNode's & DataNode's JvmMetrics objects. That is more
flexible also since we can then distinguish metrics collected from different
DFS instances (sessions).
was:
Code looks good. I have one comment - the way the objects of type JvmMetrics is
different in the NameNode/DataNode from the way they are created in
JobTracker/TaskTracker. I think it is better to have it uniform, i.e., pass
sessionId even to the NameNode's & DataNode's JvmMetrics objects. That is more
flexible also since we can then distinguish metrics collected from different
DFS instances (sessions).
> 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
>
>
> 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.
