You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "chan (Jira)" <ji...@apache.org> on 2020/08/26 03:25:00 UTC
[jira] [Resolved] (YARN-10395) ReservedContainer Node is added to
blackList of application due to this node can not allocate other container
[ https://issues.apache.org/jira/browse/YARN-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
chan resolved YARN-10395.
-------------------------
Resolution: Fixed
> 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
> Fix For: 2.9.2
>
> Attachments: Yarn-10395-001.patch
>
>
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org