[jira] Commented: (HADOOP-7144) Expose JMX with something like JMXProxyServlet

["Todd Lipcon (JIRA)" <ji...@apache.org>]

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

Todd Lipcon commented on HADOOP-7144:
-------------------------------------

Seems pretty reasonable. Though the proliferation of metrics endpoints is a little strange - a lot of this stuff (but not all) is also available via the hadoop metrics system at /metrics.

Is there some guiding principle we should follow when deciding whether to add things via JMX vs via Metrics? I always tend towards Metrics since you can use a jmx metrics context to expose them to JMX consumers, whereas the reverse is not true.

> 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
>              Labels: jmx
>             Fix For: 0.23.0
>
>
> 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