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 "Konstantinos Karanasos (JIRA)" <ji...@apache.org> on 2018/04/03 15:37:00 UTC
[jira] [Updated] (YARN-8112) Fix min cardinality check when
source==target tag in intra-app constraints
[ https://issues.apache.org/jira/browse/YARN-8112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantinos Karanasos updated YARN-8112:
-----------------------------------------
Summary: Fix min cardinality check when source==target tag in intra-app constraints (was: Relax cardinality check for intra-app affinity placement constraints)
> Fix min cardinality check when source==target tag 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
>
> 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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org