[
https://issues.apache.org/jira/browse/YARN-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Konstantinos Karanasos updated YARN-8112:
-----------------------------------------
Description:
The min cardinality constraint is
Currently following PC doesn't work
{code:java}
-placement_spec zk=3,IN,NODE,zk
-placement_spec zk=1,IN,NODE,zk
{code}
Expectation: place 3/1 zk containers in any node of the cluster.
This is because when we do cardinality check, PC cannot be satisfied as there
is no "zk" tag placed on any node. But this is a very common user-case, hence
we need to support.
was:
Currently following PC doesn't work
{code:java}
-placement_spec zk=3,IN,NODE,zk
-placement_spec zk=1,IN,NODE,zk
{code}
Expectation: place 3/1 zk containers in any node of the cluster.
This is because when we do cardinality check, PC cannot be satisfied as there
is no "zk" tag placed on any node. But this is a very common user-case, hence
we need to support.
> Fix min cardinality check for same source and target tags in intra-app
> constraints
> ----------------------------------------------------------------------------------
>
> Key: YARN-8112
> URL: https://issues.apache.org/jira/browse/YARN-8112
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Reporter: Weiwei Yang
> Priority: Major
>
> The min cardinality constraint is
>
> Currently following PC doesn't work
> {code:java}
> -placement_spec zk=3,IN,NODE,zk
> -placement_spec zk=1,IN,NODE,zk
> {code}
> Expectation: place 3/1 zk containers in any node of the cluster.
> This is because when we do cardinality check, PC cannot be satisfied as there
> is no "zk" tag placed on any node. But this is a very common user-case, hence
> we need to support.
--
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
