You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "David Bowen (JIRA)" <ji...@apache.org> on 2007/07/04 00:45:04 UTC
[jira] Created: (HADOOP-1562) Report Java VM metrics
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
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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Status: Patch Available (was: Open)
> 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
>
>
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Status: In Progress (was: Patch Available)
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Status: Patch Available (was: Open)
> 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
>
>
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Status: Patch Available (was: In Progress)
Submitting the new patch.
> 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.
[jira] Issue Comment Edited: (HADOOP-1562) Report Java VM metrics
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (HADOOP-1562) Report Java VM metrics
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511308 ]
Hadoop QA commented on HADOOP-1562:
-----------------------------------
-1, build or testing failed
2 attempts failed to build and test the latest attachment http://issues.apache.org/jira/secure/attachment/12361449/1562_2.patch against trunk revision r554144.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/381/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/381/console
Please note that this message is automatically generated and may represent a problem with the automation system and not the patch.
> 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
>
>
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Attachment: 1562_4.patch
Patch upgraded to current trunk (just one small conflict).
> 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
> Fix For: 0.14.0
>
> Attachments: 1562.patch, 1562_1.patch, 1562_2.patch, 1562_3.patch, 1562_4.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.
[jira] Commented: (HADOOP-1562) Report Java VM metrics
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511822 ]
Devaraj Das commented on HADOOP-1562:
-------------------------------------
+1. Code looks good.
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Attachment: 1562_2.patch
Here is an updated patch with the following changes:
1 There is now a static method for initiating JVM metric reporting. There is actually no need to keep a reference to the JvmMetrics object (since it will be referenced by a Timer that it creates, and that timer runs for the lifetime of the process). So I took out the fields that were keeping such references (and which were causing warnings).
2 Where possible, I put the call to initiate JVM metrics inside the class that is collecting other metrics, so as to minimize the intrusion of metrics-related stuff in the main body of the code.
3 DFS metrics are now tagged with a session id if one is provided in the hadoop-site.xml file. This will be the case when HOD provisions DFS.
4 Added JVM metric reporting to the task sub-processes (i.e. TaskTracker.Child).
> 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
>
>
> 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.
[jira] Commented: (HADOOP-1562) Report Java VM metrics
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12511540 ]
Hadoop QA commented on HADOOP-1562:
-----------------------------------
+1
http://issues.apache.org/jira/secure/attachment/12361458/1562_3.patch applied and successfully tested against trunk revision r554811.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/391/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/391/console
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Status: Open (was: Patch Available)
Withdrawing this version of the patch since I'd like to make the metrics-related code better encapsulated. Also, while I'm changing this part of the system anyway, Nigel suggested it would be useful to attach the session id to DFS metrics too.
> 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
>
>
> 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.
[jira] Commented: (HADOOP-1562) Report Java VM metrics
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510825 ]
Hadoop QA commented on HADOOP-1562:
-----------------------------------
+0, new Findbugs warnings
http://issues.apache.org/jira/secure/attachment/12361237/1562_1.patch
applied and successfully tested against trunk revision r553623,
but there appear to be new Findbugs warnings introduced by this patch.
New Findbugs warnings: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/372/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/372/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/372/console
> 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
>
>
> 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.
[jira] Commented: (HADOOP-1562) Report Java VM metrics
Posted by "Devaraj Das (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12510220 ]
Devaraj Das commented on HADOOP-1562:
-------------------------------------
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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Attachment: 1562_1.patch
Here's an updated patch with the following changes:
1 Incorporates Devaraj's suggestion of tagging DFS and NameNode jvm metrics with the session id, if there is one.
2 Adds jvm metrics reporting to SecondaryNameNode.
3 Adds event counting via a custom Log4J Appender. This tracks the number of INFO, WARN, ERROR and FATAL logging events, and reports those numbers along with the rest of the JVM metrics.
> 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
>
>
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1562:
---------------------------------
Resolution: Fixed
Status: Resolved (was: Patch Available)
I just committed this. Thanks, David!
> 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
> Fix For: 0.14.0
>
> Attachments: 1562.patch, 1562_1.patch, 1562_2.patch, 1562_3.patch, 1562_4.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.
[jira] Commented: (HADOOP-1562) Report Java VM metrics
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12512659 ]
Hadoop QA commented on HADOOP-1562:
-----------------------------------
+1
http://issues.apache.org/jira/secure/attachment/12361721/1562_4.patch applied and successfully tested against trunk revision r555813.
Test results: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/409/testReport/
Console output: http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/409/console
> 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
> Fix For: 0.14.0
>
> Attachments: 1562.patch, 1562_1.patch, 1562_2.patch, 1562_3.patch, 1562_4.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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Status: Patch Available (was: Open)
> 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
> Fix For: 0.14.0
>
> Attachments: 1562.patch, 1562_1.patch, 1562_2.patch, 1562_3.patch, 1562_4.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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Doug Cutting updated HADOOP-1562:
---------------------------------
Fix Version/s: 0.14.0
Status: Open (was: Patch Available)
Sorry, this no longer applies to the current trunk. Can you please update it? Thanks!
> 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
> Fix For: 0.14.0
>
> 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.
[jira] Updated: (HADOOP-1562) Report Java VM metrics
Posted by "David Bowen (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HADOOP-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Bowen updated HADOOP-1562:
--------------------------------
Attachment: 1562.patch
Here is a patch for review. Are there other VM-related metrics that we could usefully capture?
> 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.