[
https://issues.apache.org/jira/browse/YARN-7822?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16341147#comment-16341147
]
Konstantinos Karanasos commented on YARN-7822:
----------------------------------------------
Hi [~cheersyang], so maxCardinality does a check of <= at the state of the
cluster before the allocation that is currently being attempted. In your case,
you have maxCard=3, so n1 is a valid node as it has 3. Indeed after the
allocation it will end up having 4, so you would have to make your maxCard=2 to
have at most 3, since we are looking at the pre-allocation state. I had
mentioned this case in a comment somewhere.
> Constraint satisfaction checker support for composite OR and AND constraints
> ----------------------------------------------------------------------------
>
> Key: YARN-7822
> URL: https://issues.apache.org/jira/browse/YARN-7822
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Arun Suresh
> Assignee: Weiwei Yang
> Priority: Major
> Attachments: YARN-7822-YARN-6592.001.patch
>
>
> JIRA to track changes to {{PlacementConstraintsUtil#canSatisfyConstraints}}
> handle OR and AND Composite constaints
--
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
