[
https://issues.apache.org/jira/browse/HADOOP-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13724028#comment-13724028
]
Luke Lu commented on HADOOP-9160:
---------------------------------
bq. I don't like the prospect of having yet another RPC mechanism to do the
same thing.
While it's usually not good to duplicate code for the underlying mechanisms,
it's usually a good thing (adds customer value) to provide alternative access
points for the underlying mechanisms. Example, WebHDFS, NFS-HDFS gateways,
HttpFS etc. There is also added benefits of redundancy for admin protocols as I
mentioned in my [previous comment|#comment-13549249].
It's also false that they "do the same thing". Here is an example that the
current RPC mechanism cannot do at all: third party JVM agents that provide
advanced runtime monitoring and tuning of JVM that expose JMX as the API.
Jolokia can provide Hadoop auth to such extensions with zero code change.
> 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
