Jian He commented on YARN-2920:

- typo: {{// if we a previously running NM, we need notify scheduler about this 
- we can send an event with a list of nodes
        if (oldNM != null && rmDispatcher != null) {
              new NodeLabelsUpdateSchedulerEvent(nodeId, newLabels));
- use volatile keyword for the reference?
- how about containers running on a node without label, and now we are adding a 
- this condition check is unnecessary
    if (null == labels) {
      labels = CommonNodeLabelsManager.EMPTY_STRING_SET;

> 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
> 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

Reply via email to