Luke Lu created HADOOP-9160:
-------------------------------
Summary: 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
