[
https://issues.apache.org/jira/browse/YARN-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331841#comment-16331841
]
Weiwei Yang commented on YARN-7763:
-----------------------------------
Hi [~kkaranasos]
Thanks for the clarification, +1 for the idea that each level of constraint can
be more restrictive that upper level constraint, but not less restrictive. We
need to define the behavior how we merge constraints when there is several
ones, we can have more discussion in a followup JIRA. For this one, do you have
any more comments before it can be committed? Please let me know, thanks.
> Allow Constraints specified in the SchedulingRequest to override application
> level constraints
> ----------------------------------------------------------------------------------------------
>
> Key: YARN-7763
> URL: https://issues.apache.org/jira/browse/YARN-7763
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Wangda Tan
> Assignee: Weiwei Yang
> Priority: Blocker
> Attachments: YARN-7763-YARN-6592.001.patch,
> YARN-7763-YARN-6592.002.patch, YARN-7763-YARN-6592.003.patch
>
>
> As I mentioned on YARN-6599, we will add SchedulingRequest as part of the
> PlacementConstraintUtil method and both of processor/scheduler implementation
> will use the same logic. The logic looks like:
> {code:java}
> PlacementConstraint pc = schedulingRequest.getPlacementConstraint();
> If (pc == null) {
> pc =
> PlacementConstraintMgr.getPlacementConstraint(schedulingRequest.getAllocationTags());
> }
> // Do placement constraint match ...{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
