yehuanhuan commented on YARN-10395:

The same problem exists in fairscheduler. And this problem can be solved in 

> ReservedContainer Node is added to blackList of application due to this node 
> can not allocate other container
> -------------------------------------------------------------------------------------------------------------
>                 Key: YARN-10395
>                 URL: https://issues.apache.org/jira/browse/YARN-10395
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 2.9.2
>            Reporter: chan
>            Priority: Major
> Now,if a app reserved a node,but the node is added to app`s blacklist.
> when this node send  heartbeat to resourcemanager,the reserved container 
> allocate fails,it will make this node can not allocate other container even 
> thought this node have enough memory or vcores.so i think we can release this 
> reserved container when the reserved node is in the black list of this app.

This message was sent by Atlassian Jira

To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to