You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Weiwei Yang (JIRA)" <ji...@apache.org> on 2018/05/01 01:54:00 UTC

[jira] [Commented] (YARN-8195) Fix constraint cardinality check in the presence of multiple target allocation tags

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

Weiwei Yang commented on YARN-8195:
-----------------------------------

Thanks [~kkaranasos]!

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