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

Hadoop QA commented on HADOOP-7144:
-----------------------------------

-1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12480460/jmx.json
  against trunk revision 1127811.

    +1 @author.  The patch does not contain any @author tags.

    -1 tests included.  The patch doesn't appear to include any new or modified 
tests.
                        Please justify why no new tests are needed for this 
patch.
                        Also please list what manual steps were performed to 
verify this patch.

    -1 patch.  The patch command could not apply the patch.

Console output: 
https://builds.apache.org/hudson/job/PreCommit-HADOOP-Build/526//console

This message is automatically generated.

> 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