ok, it make sense to me. one query on these two types:
how to use it in the future if I want to specify both of them within one submit command: consider this case: 1. Partitions node label is devteam 2. Constraints node label are: glibc.version >= 2.20 && JDK.version >= 8u20 && x86_64 Thanks, Allen At 2015-12-18 16:13:15, "Naganarasimha G R (Naga)" <[email protected]> wrote: >Hi Allen, > >Node Labels are of 2 types >Partitions and Constraints, > >With Partition labels you will be able get the resource gurantees and it >almost works like a cluster within a cluster. node_label_expression for a >resource request can mention only one partition ! >and Constraints are like attributes for a node. >As per the existing design expressions like the ones you mentioned are planned >to be given only for constraints. Constraints are not yet supported yet. >(YARN-3409) > >Hope this helps, > >+ Naga >________________________________________ >From: Allen Zhang [[email protected]] >Sent: Thursday, December 17, 2015 19:55 >To: [email protected] >Subject: does yarn 2.7.1 really support label expr like && or || ? > >Hi All, > > >Well, my distributedshell works very well with "--shell_command ls >-node_label_expression aaa" >and I added a new label named "bbb" and tried this: >bin/hadoop jar >share/hadoop/yarn/hadoop-yarn-applications-distributedshell-2.7.1.jar >org.apache.hadoop.yarn.applications.distributedshell.Client --jar >share/hadoop/yarn/hadoop-yarn-applications-distributedshell-2.7.1.jar >--shell_command ls -node_label_expression "aaa || bbb" > > >I seems not work and it has been waiting for container for a long time. does >YARN 2.7.1 really support label expr like && or || ? > > > > > > >Thanks, >Allen > > > >At 2015-12-17 22:00:29, "Allen Zhang" <[email protected]> wrote: >> >> >> >>Response to myself: >> >> >>well, this JIRA really helped me: YARN-2502 >> >> >>hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-distributedshell/src/test/java/org/apache/hadoop/yarn/applications/distributedshell/TestDistributedShell.java >> >> >>what surprise me is that it set >>"yarn.scheduler.capacity.root.accessible-node-labels" with the label x and >>set "yarn.scheduler.capacity.root.accessible-node-labels.x.capacity" as 100 >> >> >>I do think I missed that, ALSO I do think it should document somewhere in >>YARN doc for other people. >> >> >>Thanks, >>Allen >> >> >> >>At 2015-12-17 16:26:19, "Allen Zhang" <[email protected]> wrote: >>>Hi All, >>> >>> >>>I am using Hadoop 2.7.1. I have 4 vms(dev, sut-1, sut-2, sut3), but I cannot >>>submit my app to YARN. very appreciate for any help:) >>> >>> >>>what I did is: >>> >>> >>>Add this to yarn-site.xml file: >>><property> >>> <name>yarn.node-labels.enabled</name> >>> <value>true</value> >>></property> >>><property> >>> <name>yarn.node-labels.fs-store.root-dir</name> >>> <value>file:///tmp/</value> >>></property> >>> >>> >>>Add this to capacity-scheduler.xml file: >>><property> >>> <name>yarn.scheduler.capacity.root.default.accessible-node-labels</name> >>> <value>aaa</value> >>></property> >>> >>> >>> >>> >>>1. bin/yarn rmadmin -addToClusterNodeLabels aaa >>>2. bin/yarn rmadmin -replaceLabelsOnNode sut-1=aaa >>>3. bin/yarn rmadmin -refreshQueues >>> >>> >>> >>> >>>the command I was trying to submit is: >>>bin/hadoop jar >>>share/hadoop/yarn/hadoop-yarn-applications-distributedshell-2.7.1.jar >>>org.apache.hadoop.yarn.applications.distributedshell.Client --jar >>>share/hadoop/yarn/hadoop-yarn-applications-distributedshell-2.7.1.jar >>>--shell_command ls -node_label_expression aaa >>> >>> >>>Thanks, >>>Allen
