hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Weiwei Yang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-7763) Allow Constraints specified in the SchedulingRequest to override application level constraints
Date Fri, 19 Jan 2018 07:08:00 GMT

    [ https://issues.apache.org/jira/browse/YARN-7763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16331834#comment-16331834

Weiwei Yang commented on YARN-7763:

Hi [~kkaranasos]

Thanks for the comments, here is my thoughts
{quote}{quote}we should do an instanceof SingleConstraint before the cast
I did not do that because I think we should have something better than {{instanceof}} to
tell which constraint we are dealing with. E.g would a {{getType}} possible ? That was why
I added a TODO in {{canSatisfyConstraints}} as a placeholder to handle other type of constraints.
{quote}{quote}constraint priority
Hmm... I was thinking the other way around. This way I can have cluster admin to setup some
basic constraints applied to all apps, and at the same time allow app/user to override constraints
if they have special requirement. The behavior you described sounds like for a certain allocation
tag, once defined in global constraint, that constraint will apply to everywhere; which means
it won't allow different constraint for one same tag. How to allow customization in this case? 



> 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
> {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

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

View raw message