hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Philip Zeyliger (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9160) Adopt Jolokia as the JMX HTTP/JSON bridge.
Date Tue, 30 Jul 2013 17:59:53 GMT

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

Philip Zeyliger commented on HADOOP-9160:

>  third party JVM agents that provide advanced runtime monitoring and tuning of JVM that
expose JMX as the API

If you're running a third party JVM agent, by all means let it expose whatever APIs it would
like--it's got everything it needs to bind to addresses and listen for 'em.  

I have no particular objections to alternative access endpoints (e.g., NFS proxies), though
it's notable that most of them are out of process proxies.  Furthermore, for distributed systems
like HDFS, you still often need a client shim to deal with HA and querying for data from the
wrong machine.  I'd never use HTTPFS from certain types of programs because then I'd have
to manually re-write all the nice retry and error-handling that DFSClient provides me.  I
do have objections to alternatives for write access.  I completely agree with Allen W: we've
got to have a way to turn it off.

BTW, one way to add administrative APIs is to add plugins.  Hue, for example, used a plugin
to datanodes and namenodes to get at some stuff.  It's not pretty, but, hey, the maintenance
burden is on the right place.
> 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

View raw message