[
https://issues.apache.org/jira/browse/YARN-7778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16351109#comment-16351109
]
Hudson commented on YARN-7778:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #13608 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/13608/])
YARN-7778. Merging of placement constraints defined at different levels.
(kkaranasos: rev 50723889cc29e8dadfa6ab6afbb90ac798d66878)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/placement/TestSingleConstraintAppPlacementAllocator.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/constraint/MemoryPlacementConstraintManager.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/constraint/PlacementConstraintsUtil.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/constraint/PlacementConstraintManager.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/constraint/TestPlacementConstraintManagerService.java
> Merging of placement constraints defined at different levels
> ------------------------------------------------------------
>
> Key: YARN-7778
> URL: https://issues.apache.org/jira/browse/YARN-7778
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Konstantinos Karanasos
> Assignee: Weiwei Yang
> Priority: Major
> Fix For: 3.1.0
>
> Attachments: Merge Constraints Solution.pdf,
> YARN-7778-YARN-7812.001.patch, YARN-7778-YARN-7812.002.patch,
> YARN-7778.003.patch, YARN-7778.004.patch
>
>
> When we have multiple constraints defined for a given set of allocation tags
> at different levels (i.e., at the cluster, the application or the scheduling
> request level), we need to merge those constraints.
> Defining constraint levels as cluster > application > scheduling request,
> constraints defined at lower levels should only be more restrictive than
> those of higher levels. Otherwise the allocation should fail.
> For example, if there is an application level constraint that allows no more
> than 5 HBase containers per rack, a scheduling request can further restrict
> that to 3 containers per rack but not to 7 containers per rack.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
