hadoop-common-issues mailing list archives

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

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

Luke Lu commented on HADOOP-7144:
---------------------------------

bq. is the package OK org.apache.hadoop.jmx? is the URL OK /jmx?
bq. where would be an appropriate place to document this?

package-info.java for javadoc would be a start.

bq. 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.

We need read-only access and have it return JSON, something like this:

{noformat}
  [ 
    { 
      "bean": "Hadoop:service=...",
      "attrs": {
        "attr1": "value1",
        ...
        "attrn": "valuen"
      }
    },
    ...
  ]
{noformat}

We also need a way to return a pre-configured set of attributes.

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

Mime
View raw message