[
https://issues.apache.org/jira/browse/YARN-2920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Wangda Tan updated YARN-2920:
-----------------------------
Attachment: YARN-2920.5.patch
bq. getUsedResources-> getUsedResourcesByLabel
And
bq. RMNodeLabelsManager constructor can pass rmContext, instead of a separate
setRMDispatcher method
Make sense to me, updated.
bq. AM container is killed as well, should we not kill the am container until
the max-am-percentage is met, similar to preemption?
This needs update internal used resource for LeafQueue/ParentQueue. With
YARN-2498, containers will not be immediately killed, and preemption policy
will handle that, AM is already last killed by preemption policy.
Thanks,
Wangda
> CapacityScheduler should be notified when labels on nodes changed
> -----------------------------------------------------------------
>
> Key: YARN-2920
> URL: https://issues.apache.org/jira/browse/YARN-2920
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Attachments: YARN-2920.1.patch, YARN-2920.2.patch, YARN-2920.3.patch,
> YARN-2920.4.patch, YARN-2920.5.patch
>
>
> Currently, labels on nodes changes will only be handled by
> RMNodeLabelsManager, but that is not enough upon labels on nodes changes:
> - Scheduler should be able to do take actions to running containers. (Like
> kill/preempt/do-nothing)
> - Used / available capacity in scheduler should be updated for future
> planning.
> We need add a new event to pass such updates to scheduler
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
