[
https://issues.apache.org/jira/browse/MAPREDUCE-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494673#comment-13494673
]
Hudson commented on MAPREDUCE-4666:
-----------------------------------
Integrated in Hadoop-Mapreduce-trunk #1253 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1253/])
MAPREDUCE-4666. JVM metrics for history server. (jlowe via jeagles)
(Revision 1407669)
Result = FAILURE
jeagles :
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1407669
Files :
* /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-mapreduce-project/hadoop-mapreduce-client/hadoop-mapreduce-client-hs/src/main/java/org/apache/hadoop/mapreduce/v2/hs/JobHistoryServer.java
> 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
> Assignee: Jason Lowe
> Priority: Minor
> Fix For: 3.0.0, 2.0.3-alpha, 0.23.5
>
> 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
