[
https://issues.apache.org/jira/browse/YARN-311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13544082#comment-13544082
]
Todd Lipcon commented on YARN-311:
----------------------------------
Per the discussion in HADOOP-9160, I really don't think we should add anything
which is only available over JMX. The security model, for one, is wildly
incompatible with the rest of Hadoop security.
If the main reason for wanting JMX is so that other software can call these
RPCs without the Hadoop jar, I'll counter and say we should go even farther and
allow other software to not even require a JVM. I see two ways of doing this:
1) Implement a simple client in C or Python which speaks Hadoop RPC via protobuf
2) Add REST interfaces.
I am in favor of doing option 1. A single-threaded blocking RPC client without
any connection pooling, etc, is not very difficult to write, and for
administrative purposes that would be sufficient, right? If we had such a thing
available as a relatively small C or python library available, would that solve
the issue just as well?
> Dynamic node resource configuration on RM with JMX interface
> ------------------------------------------------------------
>
> Key: YARN-311
> URL: https://issues.apache.org/jira/browse/YARN-311
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager, scheduler
> Reporter: Junping Du
> Assignee: Junping Du
>
> As the first step, we go for resource change on RM side and expose JMX API.
> For design details, please refer proposal and discussion in parent JIRA:
> YARN-291.
--
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
