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

Bilwa S T updated YARN-10397:
-----------------------------
    Description: 
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}

 

  was:
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}
I think we should make this configurable
 


> 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
>            Reporter: Bilwa S T
>            Assignee: Bilwa S T
>            Priority: Major
>
> 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.3.4#803005)

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

Reply via email to