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 "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2025/10/04 00:21:00 UTC

[jira] [Commented] (YARN-11643) Skip unnecessary pre-check in Multi Node Placement

    [ https://issues.apache.org/jira/browse/YARN-11643?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024618#comment-18024618 ] 

ASF GitHub Bot commented on YARN-11643:
---------------------------------------

github-actions[bot] commented on PR #6426:
URL: https://github.com/apache/hadoop/pull/6426#issuecomment-3367612458

   We're closing this stale PR because it has been open for 100 days with no activity. This isn't a judgement on the merit of the PR in any way. It's just a way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working on it, please feel free to re-open it and ask for a committer to remove the stale tag and review again.
   Thanks all for your contribution.




> Skip unnecessary pre-check in Multi Node Placement
> --------------------------------------------------
>
>                 Key: YARN-11643
>                 URL: https://issues.apache.org/jira/browse/YARN-11643
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>            Reporter: Xie YiFan
>            Assignee: Xie YiFan
>            Priority: Minor
>              Labels: pull-request-available
>
> When Multi Node Placement enabled, RegularContainerAllocator do a while loop to find one node from candidate set to allocate for a given scheduler key. Before do allocate, pre-check be called to check if current node satisfies check. If this node does not pass all checks, just continue to next node.
> {code:java}
> if (reservedContainer == null) {
>   result = preCheckForNodeCandidateSet(node,
>       schedulingMode, resourceLimits, schedulerKey);
>   if (null != result) {
>     continue;
>   }
> } {code}
> But some checks are related to scheduler Key or Application which return PRIORITY_SKIPPED or APP_SKIPPED. It means that if first node does not pass check, the following nodes also do not pass. 
> If cluster have 5000 nodes in default partition, Scheduler will waste 5000 times loop for just one scheduler key.
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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