Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Thu, 1 Aug 2013 11:31:51 +0000 (UTC)
From: "Steve Loughran (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12624782.1355993142871.151205.1375356711496@arcas>
In-Reply-To: <JIRA.12624782.1355993142871@arcas>
References: <JIRA.12624782.1355993142871@arcas>
Subject: [jira] [Commented] (HADOOP-9160) Adopt Jolokia as the JMX HTTP/JSON
 bridge.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Steve Loughran commented on HADOOP-9160:
----------------------------------------

While I don't have a personal need for this, if the option can be made low cost to add to Hadoop, with some regression tests, there's no obvious harm in adding the feature. built-in JMX has always sucked; we used to us MX4J for that reason.

Looking at the patch some more, HttpServer won't start up if jolokia isn't on the classpath. That is something I'd reject. Better to

# mark JAR as optional in the POM
# make the servlet registration work even if jolokia isn't on the classpath (dynamic class load or separate class to do the registration -a class only invoked iff jolokia is enabled)
                
> Adopt Jolokia as the JMX HTTP/JSON bridge.
> ------------------------------------------
>
>                 Key: HADOOP-9160
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9160
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Luke Lu
>            Assignee: Junping Du
>              Labels: features
>         Attachments: hadoop-9160-demo-branch-1.txt, HADOOP-9160.patch
>
>
> The current JMX HTTP bridge has served its purpose, while a more complete solution: Jolokia (formerly Jmx4Perl) has been developed/matured over the years.
> Jolokia provides comprehensive JMX features over HTTP/JSON including search and list of JMX attributes and operations metadata, which helps to support inter framework/platform compatibility. It has first class language bindings for Perl, Python, Javascript, Java.
> It's trivial (see demo patch) to incorporate Jolokia servlet into Hadoop HTTP servers and use the same security mechanisms.
> Adopting Jolokia will substantially improve the manageability of Hadoop and its ecosystem.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira