You are viewing a plain text version of this content. The canonical link for it is here.

Posted to mapreduce-issues@hadoop.apache.org by "Jason Lowe (JIRA)" <ji...@apache.org> on 2012/11/08 22:44:12 UTC

[jira] [Updated] (MAPREDUCE-4666) JVM metrics for history server

     [ https://issues.apache.org/jira/browse/MAPREDUCE-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated MAPREDUCE-4666:
----------------------------------

    Attachment: MAPREDUCE-4666.patch

Patch to add metrics2 JvmMetrics to the history server.  I manually tested this to verify the metrics could be used via a sink configured in hadoop-metrics2.properties.  I also verified the JvmMetrics bean shows up via the JMX web service.
                
> JVM metrics for history server
> ------------------------------
>
>                 Key: MAPREDUCE-4666
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4666
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>          Components: jobhistoryserver
>    Affects Versions: 2.0.2-alpha
>            Reporter: Jason Lowe
>            Priority: Minor
>         Attachments: MAPREDUCE-4666.patch
>
>
> It would be nice if the job history server provided the same JVM metrics via metrics2 that other Hadoop daemons are already providing.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira