hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Joseph Evans (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-7144) Expose JMX with something like JMXProxyServlet
Date Fri, 20 May 2011 14:28:47 GMT

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

Robert Joseph Evans updated HADOOP-7144:

    Attachment: HADOOP-7411-trunk-alpha.patch

I have attached an initial patch pulling in JMXProxyServlet.java from Tomcat 7.0.14.
I pulled over two classes  and part of a third.  

org.apache.tomcat.util.ExceptionUtils - only the package name changed.

org.apache.tomcat.util.modeler.Registry - two methods from this class were moved into JMXProxyServlet
getType and convertValue and modified to use mBeanServer from JMXProxyServlet instead of the
MBeanServer from Registry

org.apache.catalina.manager.JMXProxyServlet - pacakge name changed.  Registry was removed
and replaced with a direct call to get MBeanServer, and two private methods.

There are no tests and no documentation changes right now (Which is why I marked it alpha).
 I wanted feedback on it first.

1) is the package OK org.apache.hadoop.jmx?
2) is the URL OK /jmx?
3) where would be an appropriate place to document this?
4) is this even the right thing to do?  I am not sure how standard the format is.  I need
to dig into it a bit more to really understand it, because all I have done is a simple port.

> 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: Luke Lu
>              Labels: jmx
>             Fix For: 0.23.0
>         Attachments: HADOOP-7411-trunk-alpha.patch
> 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
> 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

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

View raw message