[
https://issues.apache.org/jira/browse/YARN-8195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16458914#comment-16458914
]
Hudson commented on YARN-8195:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #14092 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/14092/])
YARN-8195. Fix constraint cardinality check in the presence of multiple
(kkaranasos: rev 9b0955545174abe16fd81240db30f175145ee89b)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/constraint/TestPlacementConstraintsUtil.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
> Fix constraint cardinality check in the presence of multiple target
> allocation tags
> -----------------------------------------------------------------------------------
>
> Key: YARN-8195
> URL: https://issues.apache.org/jira/browse/YARN-8195
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Weiwei Yang
> Assignee: Weiwei Yang
> Priority: Critical
> Fix For: 3.2.0, 3.1.1
>
> Attachments: YARN-8195.001.patch, YARN-8195.002.patch
>
>
> While testing PC with multiple allocation tags, I found the behavior is not
> working as expected. To demonstrate this issue, imagine we have following PC
> {code}
> X=1, notin,node, A, B
> {code}
> this is to ask for a placement on a node that has no A or B.
> now assume we have A, B tags on a node with following numbers of allocations,
> {code}
> A(0), B(1)
> {code}
> expectation, as B has 1 allocation on this node, this node should not satisfy
> the PC. However in actual, it passes the check.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
