[
https://issues.apache.org/jira/browse/YARN-11107?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17517921#comment-17517921
]
Xiping Zhang commented on YARN-11107:
-------------------------------------
I think when NodeLabel is enabled, RM should consider the lable of the
application when passing the number of NM to AM ，When the number of blacklisted
nodes exceeds 33% of the total number of lable nodes, the AM releases NM in the
blacklist. for DefaultAMSProcessor.java :
{code:java}
//代码占位符
final class DefaultAMSProcessor implements ApplicationMasterServiceProcessor {
...
public void allocate(ApplicationAttemptId appAttemptId,
AllocateRequest request, AllocateResponse response) throws YarnException {
...
//Consider whether NodeLabel is enabled
response.setNumClusterNodes(getScheduler().getNumClusterNodes());
...
}
{code}
> When NodeLabel is enabled for a YARN cluster, the blacklist feature is
> abnormal
> -------------------------------------------------------------------------------
>
> Key: YARN-11107
> URL: https://issues.apache.org/jira/browse/YARN-11107
> Project: Hadoop YARN
> Issue Type: Bug
> Components: resourcemanager
> Affects Versions: 2.9.2, 3.3.0
> Reporter: Xiping Zhang
> Priority: Major
>
> Yarn NodeLabel is enabled in the production environment. We encountered a
> application AM that blacklisted all NMS corresponding to the lable in the
> queue, and other application in the queue cannot apply for computing
> resources. We found that RM printed a lot of logs "Trying to fulfill
> reservation for application..."
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
