Hi Prabhu I just did a quick look. From the scheduling request side, it should work. But the placement constraint parser in distributed shell did not parse the namespace, that looks like a missing piece. Do you want to open a ticket to track this?
Thanks Weiwei Power of Open and Collaborative, Bravo! On Jan 30, 2019, 9:35 PM +0800, Prabhu Josephraj <[email protected]>, wrote: > Hi, > > Was testing Allocation Tag NameSpace on a single node cluster (Hadoop > 3.3.0-SNAPSHOT) with two Distributed Shell Jobs. The first job requests a > container with source tag zk. > > yarn org.apache.hadoop.yarn.applications.distributedshell.Client -jar > $HADOOP_HOME/share/hadoop/yarn/hadoop-yarn-applications-distributedshell-3.3.0-SNAPSHOT.jar > -shell_command sleep -shell_args 100 -placement_spec "zk=1,NOTIN,NODE,zk" > > The second job requests container notin all/zk but it got allocated on same > node where zk container is running. [attached screenshot] > > > yarn org.apache.hadoop.yarn.applications.distributedshell.Client -jar > $HADOOP_HOME/share/hadoop/yarn/hadoop-yarn-applications-distributedshell-3.3.0-SNAPSHOT.jar > -shell_command sleep -shell_args 100 -placement_spec > "spark=1,NOTIN,NODE,all/zk" > > > <>Want to check if the command is wrong or any bug. > > Thanks, > Prabhu Joseph >
