[
https://issues.apache.org/jira/browse/YARN-10397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180774#comment-17180774
]
Bilwa S T commented on YARN-10397:
----------------------------------
Thanks [~elgoiri] for reviewing this. I have updated javadoc .
Yes this is covered by UT TestCapacitySchedulerSchedulingRequestUpdate. This
testcase checks if capacityscheduler supports placement constraint or not.
bq. BTW, I'm guessing you are using your own scheduler that supports this?
Yes we have our own scheduler which supports placement constraints.
> 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: Minor
> 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.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
