[
https://issues.apache.org/jira/browse/HADOOP-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729822#comment-13729822
]
Steve Loughran commented on HADOOP-9160:
----------------------------------------
[~jdu] hadoop projects have fairly bad practises dependency wise, especially as
to how the execution engine classpath trickles down into the MR engine
classpath. Tom's done some work there to (optionally) address that.
For this JMX thing, as it only gets used in one place, making it optional is
easy and harmless. For other bits of code that we use (e.g. the SLF4J logger
behind jetty), we may now be committed to bundling SLF4J into Hadoop even if
Jetty was switched out (e.g. transitive dependencies of our dependencies are
even affecting hadoop's code).
In the 'hadoop compatibility' doc we explicitly said "no guarantees" about our
own dependencies.
> 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
