Return-Path: 
 <mapreduce-issues-return-39074-apmail-hadoop-mapreduce-issues-archive=hadoop.apache.org@hadoop.apache.org>
X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org
Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 21C5B952C
	for <apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org>;
 Fri, 27 Jan 2012 15:38:37 +0000 (UTC)
Received: (qmail 77693 invoked by uid 500); 27 Jan 2012 15:38:36 -0000
Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org
Received: (qmail 77633 invoked by uid 500); 27 Jan 2012 15:38:36 -0000
Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:mapreduce-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:mapreduce-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:mapreduce-issues@hadoop.apache.org>
List-Id: <mapreduce-issues.hadoop.apache.org>
Reply-To: mapreduce-issues@hadoop.apache.org
Delivered-To: mailing list mapreduce-issues@hadoop.apache.org
Received: (qmail 77606 invoked by uid 99); 27 Jan 2012 15:38:35 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jan 2012 15:38:35 +0000
X-ASF-Spam-Status: No, hits=-2000.0 required=5.0
	tests=ALL_TRUSTED,T_RP_MATCHES_RCVD
X-Spam-Check-By: apache.org
Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 27 Jan 2012 15:38:33 +0000
Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116])
	by hel.zones.apache.org (Postfix) with ESMTP id C72D613540C
	for <mapreduce-issues@hadoop.apache.org>;
 Fri, 27 Jan 2012 15:38:12 +0000 (UTC)
Date: Fri, 27 Jan 2012 15:38:12 +0000 (UTC)
From: "Eric Payne (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <495630145.435.1327678692817.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <972191919.60504.1327078062132.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-3703) ResourceManager should provide
 node lists in JMX output
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394
X-Virus-Checked: Checked by ClamAV on apache.org


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

Eric Payne commented on MAPREDUCE-3703:
---------------------------------------

Actually, there are several ResourceManager beans. I couldn't find any that test JMX specifically, though, so I added a test for this new one. The ResourceManager beans are accessible via http://<rm-host>:<port>/jmx and are as follows:

Hadoop:service=ResourceManager,name=UgiMetrics (login metrics)
Hadoop:service=ResourceManager,name=MetricsSystem,sub=Stats (sources/sinks/ops/time)
Hadoop:service=ResourceManager,name=QueueMetrics,q0=root,q1=<qname>
Hadoop:service=ResourceManager,name=RpcDetailedActivityForPort<port> (NumOps/AvgTime)
Hadoop:service=ResourceManager,name=ClusterMetrics (NumNodes, but not lists of nodes)
Hadoop:service=ResourceManager,name=RMNMInfo (NEW: contains list and status of live nodes).
                
> ResourceManager should provide node lists in JMX output
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-3703
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3703
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: resourcemanager
>    Affects Versions: 0.23.1
>            Reporter: Eric Payne
>            Assignee: Eric Payne
>            Priority: Critical
>         Attachments: MAPREDUCE-3703.1.txt
>
>
> In 0.20.*, the JMX UI for the JobTracker (http://<JobTrackerHost>:50030/jmx) showed lists of Live and BlackListed Nodes under the JobTrackerInfo section.
> In 0.23, the ResourceManager JMX UI shows the number of active, decommissioned, lost, unhealthy, and rebooted nodes under the ClusterMetrics section, but does not give the list of nodes.
> At least the list of active nodes is needed in JSON format.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira