Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 9 Nov 2012 22:13:12 +0000 (UTC)
From: "Jonathan Eagles (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <2138515676.93931.1352499192677.JavaMail.jiratomcat@arcas>
In-Reply-To: <176988096.94721.1348005129291.JavaMail.jiratomcat@arcas>
Subject: [jira] [Commented] (MAPREDUCE-4666) JVM metrics for history server
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-4666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13494353#comment-13494353 ] 

Jonathan Eagles commented on MAPREDUCE-4666:
--------------------------------------------

+1. simple change that works for me.
                
> 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
>         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