hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Konstantinos Karanasos (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:07:00 GMT

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

Konstantinos Karanasos commented on YARN-7763:
----------------------------------------------

Just a small clarification to my above point about constraint priority.

Eventually we need to support constraint merging and checking constraint conflicts.

If an app-level constraints says that there should not be more than 5 hbase containers per
rack, then a scheduling request-constraint can be more restrictive (e.g., request no more
than 3 hbase per rack), but it cannot be less restrictive (e.g., request no more than 7 per
rack), because that will contradict the app-level constraint.

Until we get the constraint merging, the priority is not clear (I can see reasons for both
ways). In any case, for now it does not matter, because we don't expect to have constraints
in different levels.

> 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: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org


Mime
View raw message