Bilwa S T created YARN-10397:
--------------------------------
Summary: 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
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
--
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
