Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 26 May 2011 16:21:47 +0000 (UTC)
From: "Robert Joseph Evans (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <1457725625.45652.1306426907791.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1728703995.16605.1297739397760.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-7144) Expose JMX with something like
 JMXProxyServlet
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Robert Joseph Evans commented on HADOOP-7144:
---------------------------------------------

Hey Luke, what will it take to get HADOOP-7330 into 0.20.20X?  I looked at the patch and it looks straight forward?  It would be nice to have the JSON output consistent between releases. 

> Expose JMX with something like JMXProxyServlet 
> -----------------------------------------------
>
>                 Key: HADOOP-7144
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7144
>             Project: Hadoop Common
>          Issue Type: New Feature
>            Reporter: Luke Lu
>            Assignee: Robert Joseph Evans
>              Labels: jmx
>             Fix For: 0.23.0
>
>         Attachments: HADOOP-7411-0.20.20X-V1.patch, HADOOP-7411-trunk-V1.patch, HADOOP-7411-trunk-alpha.patch, jmx.json
>
>
> Much of the Hadoop metrics and status info is available via JMX, especially since 0.20.100, and 0.22+ (HDFS-1318, HADOOP-6728 etc.) For operations staff not familiar JMX setup, especially JMX with SSL and firewall tunnelling, the usage can be daunting. Using a JMXProxyServlet (a la Tomcat) to translate JMX attributes into JSON output would make a lot of non-Java admins happy.
> We could probably use Tomcat's JMXProxyServlet code directly, if it's already output some standard format (JSON or XML etc.) The code is simple enough to port over and can probably integrate with the common HttpServer as one of the default servelet (maybe /jmx) for the pluggable security.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira