[
https://issues.apache.org/jira/browse/YARN-9252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16758945#comment-16758945
]
Prabhu Joseph commented on YARN-9252:
-------------------------------------
Hi [~cheersyang], Have few doubts while integrating Allocation Tag Namespace
when multiple target allocation tags present, can you help me to clarify.
Currently the Expression a=1,notin,node,b,c is converted to SingleConstraint
with a TargetExpression with two allocation tags b and c under default SELF
namespace.
Does a=1,notin,node,NOT_SELF/b,SELF/c (both allocation tag has different
namespace) valid?.
If valid, which of the below PlacementConstraint need to be used.
1.SingleConstraint with two TargetExpression - the first one with allocation
tag b and namespace NOT_SELF and second one with allocation tag c and namespace
SELF.
or
2. SingleConstraint with a TargetExpression with two allocation tags - both
with it's own namespace. In this case, we don't have an API to do that,
allocationTagWithNamespace accepts one namespace for set of allocationTags, we
will need allocationTagWithNamespace accepting set of pair of namespace and
allocationTag.
If not valid, Can we support only one namespace for set of allocation tags like
a=1,notin,node,NOT_SELF,b,c. The third token can be reserved for Allocation Tag
Namespace in constraint expression.
> Allocation Tag Namespace support in Distributed Shell
> -----------------------------------------------------
>
> Key: YARN-9252
> URL: https://issues.apache.org/jira/browse/YARN-9252
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: distributed-shell
> Affects Versions: 3.1.1
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
>
> Distributed Shell supports placement constraint but allocation Tag Namespace
> is not honored.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
