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 Wed, 31 Jul 2013 18:03:52 GMT

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

Philip Zeyliger commented on HADOOP-9160:
-----------------------------------------

I'm not a committer on this project, so my comments are obviously advisory only, and if you
get support, you're welcome to disregard me.

* It sounds like you're using Jolokia not so much for the JMX-ness as for its alternative
authentication model.  Something about the tools you're handling can't handle the SPNEGO(?)
model for the HTTP-based (REST) APIs, and so you're introducing a separate HTTP server (Jolokia)
to handle that.  Is it the protocol that's causing interoporability issues or the authentication
model?  The auth models are already pluggable.  I wish we'd talk about concrete tools that
you're integrating--I'm surprised they speak Jolokia but not HTTP.

* Similarly, I'd like to understand whether, in your ideal world, you could, say, read a file
or call "hdfs upgrade" over JMX?

* We've spent considerable effort getting backwards-compatible protocols in place for the
wire protocol (via protocol buffers) and the client interfaces (via annotations).  Opening
up another layer of RPC exposes us to more issues here.




                
> 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

Mime
View raw message