[
https://issues.apache.org/jira/browse/YARN-7863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16561858#comment-16561858
]
Weiwei Yang edited comment on YARN-7863 at 7/30/18 12:33 PM:
-------------------------------------------------------------
{quote}
For DS, I think its better we correlate with placement_spec for now for better
easiness in review and api compatibility.
{quote}
+1 for this idea. This way we can specify allocation tags and node attributes
in PC expressions under same syntax.
but for this expression:
{noformat}
-placement_spec
OR(IN,python=true:NOTIN,java=1.8):IN,os!=centos:NOTIN,env=prod,dev
{noformat}
I don't think we should use ":" to represent AND. The convention was to use ":"
as the delimiter between each child of a conjunction expression (AND or OR). In
the released version of DS, referring to
[https://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/PlacementConstraints.html|https://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/PlacementConstraints.html],
{noformat}
zk=3,NOTIN,NODE,zk:hbase=5,IN,RACK,zk:spark=7,CARDINALITY,NODE,hbase,1,3
{noformat}
this actually represents 3 separate placement constraints instead of a AND with
3 children.
was (Author: cheersyang):
{quote}
For DS, I think its better we correlate with placement_spec for now for better
easiness in review and api compatibility.
{quote}
+1 for this idea. This way we can specify allocation tags and node attributes
in PC expressions under same syntax.
but for this expression:
{noformat}
-placement_spec
OR(IN,python=true:NOTIN,java=1.8):IN,os!=centos:NOTIN,env=prod,dev
{noformat}
I don't think we should use ":" to represent AND. The convention was to use ":"
as the delimiter between each child of a conjunction expression (AND or OR). In
the released version of DS, referring to
[https://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/PlacementConstraints.html|https://hadoop.apache.org/docs/r3.1.0/hadoop-yarn/hadoop-yarn-site/PlacementConstraints.html],
{noformat}
zk=3,NOTIN,NODE,zk:hbase=5,IN,RACK,zk:spark=7,CARDINALITY,NODE,hbase,1,3
{noformat}
this actually represents 3 separate placement constraints instead of a AND with
3 children.
> Modify placement constraints to support node attributes
> -------------------------------------------------------
>
> Key: YARN-7863
> URL: https://issues.apache.org/jira/browse/YARN-7863
> Project: Hadoop YARN
> Issue Type: Sub-task
> Reporter: Sunil Govindan
> Assignee: Sunil Govindan
> Priority: Major
> Attachments: YARN-7863-YARN-3409.002.patch,
> YARN-7863-YARN-3409.003.patch, YARN-7863.v0.patch
>
>
> This Jira will track to *Modify existing placement constraints to support
> node attributes.*
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
