[
https://issues.apache.org/jira/browse/YARN-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17181070#comment-17181070
]
chan commented on YARN-10395:
-----------------------------
[~yehuanhuan] yeah,but in capacityScheduler,the node will be reserved for the
app if the app still is not satisfied for a long time, so i release the
reserved container if RegularContainerAllocator#checkIfNodeBlackListed do not
return null
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
