[
https://issues.apache.org/jira/browse/YARN-3482?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14505284#comment-14505284
]
Inigo Goiri commented on YARN-3482:
-----------------------------------
[~kasha], the administration interface already has a method called
updateNodeResource which takes a map NodeId -> ResourceOption. So it basically
has the functionality that we want but it doesn't through the NodeLabeling
interface. The problem is that right now there's no way for the admin to
trigger this. So we have two options:
1) Expose this interface to the RM which is a little bit heavy as we need to
update the whole cluster.
2) Do what we planned (send on the heartbeat from the NM) and just leverage
these mechanisms.
> Report NM available resources in heartbeat
> ------------------------------------------
>
> Key: YARN-3482
> URL: https://issues.apache.org/jira/browse/YARN-3482
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: nodemanager, resourcemanager
> Affects Versions: 2.7.0
> Reporter: Inigo Goiri
> Original Estimate: 504h
> Remaining Estimate: 504h
>
> NMs are usually collocated with other processes like HDFS, Impala or HBase.
> To manage this scenario correctly, YARN should be aware of the actual
> available resources. The proposal is to have an interface to dynamically
> change the available resources and report this to the RM in every heartbeat.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
