[
https://issues.apache.org/jira/browse/YARN-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13541606#comment-13541606
]
Junping Du commented on YARN-291:
---------------------------------
Basically, there are two interfaces of updating NM's resources in current
implementation:
- YARN RPC through ClientRMProtocol to update resource on RM (RMNode and
SchedulerNode) directly (without tell NM). (In fact, this no need the change of
Heartbeat)
- JMX on NodeManager, the resource is updated on NM then going to RM through
heartbeat.
There are some other options as well:
1) Add NMAdminProtocol, so NM have RPCServer to accept resource updating
through local commandline then forward to RM through heartbeat.
2) Add RMNMProtocol (NM is server), so request through ClientRMProtocol (RM)
can go to NM (no need to change heartbeat also).
3) Add REST API on NM with put() method on resource change.
1) and 2) seems heavy to me, 3) seems like a reasonable work for next step?
> Dynamic resource configuration on NM
> ------------------------------------
>
> Key: YARN-291
> URL: https://issues.apache.org/jira/browse/YARN-291
> Project: Hadoop YARN
> Issue Type: New Feature
> Components: nodemanager, scheduler
> Reporter: Junping Du
> Assignee: Junping Du
> Labels: features
> Attachments: YARN-291-all-v1.patch
>
>
> The current Hadoop YARN resource management logic assumes per node resource
> is static during the lifetime of the NM process. Allowing run-time
> configuration on per node resource will give us finer granularity of resource
> elasticity. This allows Hadoop workloads to coexist with other workloads on
> the same hardware efficiently, whether or not the environment is virtualized.
> About more background and design details, please refer: HADOOP-9165.
--
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
