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] [Commented] (HADOOP-7144) Expose JMX with something like JMXProxyServlet
Date Tue, 31 May 2011 22:17:47 GMT

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

Robert Joseph Evans commented on HADOOP-7144:

It is there because that is what tomcat is doing inside their JMXProxy Servlet which I modified,
and didn't take the time to understand all of the possible exceptions that could be thrown
in each of the cases to clean it up.

Part of the reason for ignoring the exceptions is because JMX can execute arbitrary code inside
the JMXBeans, which could throw all kinds of exceptions.  Ideally we would like the code to
be robust so that if some beans are causing issues that we can still output data for the rest
of the beans.  But I will look at what it takes to clean up the exception handling.

> 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,
> 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