hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Loughran (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-9160) Change management protocol to JMX
Date Fri, 21 Dec 2012 13:45:14 GMT

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

Steve Loughran commented on HADOOP-9160:
----------------------------------------

I've been arguing for a decade that JMX support should be built in from the outset:
 [http://www.hpl.hp.com/techreports/2002/HPL-2002-274.pdf] -the flaw being that JMX was initially
a plugin point for proprietary management tools (Tivoli, OpenView, ...) without any wire protocol.
As such, it was a tool for ops -not dev, and so never got built in early on. If you could
make it easier for the devs to use JMX for debug and testing, then maybe you'd get better
support.

I don't see any reason not to make JMX an option -It'd be great to be able to hook up a NN
and see both system behaviour and the JVM monitoring points at the same time. It's just as
the others say -"instead" is a pretty bold move. 
                
> Change management protocol to JMX
> ---------------------------------
>
>                 Key: HADOOP-9160
>                 URL: https://issues.apache.org/jira/browse/HADOOP-9160
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Luke Lu
>
> Currently we use Hadoop RPC (and some HTTP, notably fsck) for admin protocols. We should
consider moving all admin protocols to JMX, as it's the industry standard for java server
management with wide client support.
> Having an alternative/redundant RPC mechanism is very desirable for admin protocols.
I've seen in the past in multiple cases, where NN and/or JT RPC were locked up solid due to
various bugs and/or RPC thread pool exhaustion, while HTTP and/or JMX worked just fine.
> Other desirable benefits include admin protocol backward compatibility and introspectability,
which is convenient for a centralized management system to manage multiple Hadoop clusters
of different versions. Another notable benefit is that it's much easier to implement new admin
commands in JMX (especially with MXBean) than Hadoop RPC, especially in trunk (and 0.23+,
2.x).
> Since Hadoop RPC doesn't guarantee backward compatibility (probably not ever for branch-1),
there are no external management tools depending on it. We can maintain a practical backward
compatibility by keeping the admin script/command line interface unchanged.

--
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