[
https://issues.apache.org/jira/browse/HADOOP-9160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13725307#comment-13725307
]
Junping Du commented on HADOOP-9160:
------------------------------------
Thanks Steve for comments.
bq. I can see the merit in having some of the write ops accessible to "legacy"
management tools, esp. the ones the netops people are happy with.
Agree.
bq. some needless IDE-cleanups that could be separated out (maybe)
Sorry. It is by myself not IDE actually. I know we should address this
separately...but always cannot bear warnings... Will separate it out in next
patch.
bq. tests, need tests. Does the servlet come up, does it support both the read
and write operations?
Will do. The patch hasn't been completed yet and still missing component here.
It should enable agent model of jolokia that allow read/write in case JMX API
allows (jolokia plays as adaptor layer between HTTP/JSON request and JMX
interface). Will do more tests later.
> 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
