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

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

Ahh, Really Jenkins tried to use the JSON as a patch?  Oh well the following 
are the manual results for trunk
     [exec] +1 overall.  
     [exec] 
     [exec]     +1 @author.  The patch does not contain any @author tags.
     [exec] 
     [exec]     +1 tests included.  The patch appears to include 4 new or 
modified tests.
     [exec] 
     [exec]     +1 javadoc.  The javadoc tool did not generate any warning 
messages.
     [exec] 
     [exec]     +1 javac.  The applied patch does not increase the total number 
of javac compiler warnings.
     [exec] 
     [exec]     +1 findbugs.  The patch does not introduce any new Findbugs 
(version 1.3.9) warnings.
     [exec] 
     [exec]     +1 release audit.  The applied patch does not increase the 
total number of release audit warnings.
     [exec] 
     [exec]     +1 system test framework.  The patch passed system test 
framework compile.
     [exec] 


> 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

Reply via email to