Brook Zhou commented on YARN-3223:

Makes sense. 

One thing that I'm not sure about - RMNodeImpl does not know directly the 
amount of usedResource in order to trigger an RMNodeResourceUpdateEvent. I can 
use rmNode.context.getScheduler().(rmNode.getNodeID()).getUsedResource(), but 
I'm not sure if adding that dependency on scheduler is okay.

> Resource update during NM graceful decommission
> -----------------------------------------------
>                 Key: YARN-3223
>                 URL: https://issues.apache.org/jira/browse/YARN-3223
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: nodemanager, resourcemanager
>    Affects Versions: 2.7.1
>            Reporter: Junping Du
>            Assignee: Brook Zhou
>         Attachments: YARN-3223-v0.patch, YARN-3223-v1.patch, 
> YARN-3223-v2.patch
> During NM graceful decommission, we should handle resource update properly, 
> include: make RMNode keep track of old resource for possible rollback, keep 
> available resource to 0 and used resource get updated when
> container finished.

This message was sent by Atlassian JIRA

Reply via email to