[ 
https://issues.apache.org/jira/browse/YARN-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Shilun Fan updated YARN-10397:
------------------------------
          Component/s: capacity scheduler
     Target Version/s: 3.3.1, 3.4.0
    Affects Version/s: 3.3.1
                       3.4.0

> SchedulerRequest should be forwarded to scheduler if custom scheduler 
> supports placement constraints
> ----------------------------------------------------------------------------------------------------
>
>                 Key: YARN-10397
>                 URL: https://issues.apache.org/jira/browse/YARN-10397
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>    Affects Versions: 3.4.0, 3.3.1
>            Reporter: Bilwa S T
>            Assignee: Bilwa S T
>            Priority: Minor
>             Fix For: 3.4.0, 3.3.1
>
>         Attachments: YARN-10397.001.patch, YARN-10397.002.patch
>
>
> Currently only CapacityScheduler supports placement constraints so request 
> gets forwarded only for capacityScheduler. Below exception will be thrown if 
> custom scheduler supports placement constraint
> {code:java}
> if (request.getSchedulingRequests() != null
>         && !request.getSchedulingRequests().isEmpty()) {
>       if (!(scheduler instanceof CapacityScheduler)) {
>         String message = "Found non empty SchedulingRequest of "
>             + "AllocateRequest for application=" + appAttemptId.toString()
>             + ", however the configured scheduler="
>             + scheduler.getClass().getCanonicalName()
>             + " cannot handle placement constraints, rejecting this "
>             + "allocate operation";
>         LOG.warn(message);
>         throw new YarnException(message);
>       }
>     }
> {code}
>  



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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to