[ https://issues.apache.org/jira/browse/YARN-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16143458#comment-16143458 ]
Prabhu Joseph commented on YARN-7108: ------------------------------------- Have submitted a mapreduce job with default queue and no label settings. {code} hadoop jar hadoop-mapreduce-examples-2.7.3.jar wordcount /Input /Output {code} > Refreshing Default Node Label Expression of a queue does not reflect for > running apps > ------------------------------------------------------------------------------------- > > Key: YARN-7108 > URL: https://issues.apache.org/jira/browse/YARN-7108 > Project: Hadoop YARN > Issue Type: Bug > Components: capacity scheduler > Affects Versions: 2.7.3 > Reporter: Prabhu Joseph > > Refreshing a queue's default node label expression does not reflect for the > running applications. > Repro Steps: > 4 node cluster, two node labels label1 and label2. label1 is Exclusive > Partition with Node1 and Node2, label2 is Exclusive Partition with Node3 and > Node4. A default queue whose default node label expression is label1. > 1.Shutdown NodeManagers on label1 nodes Node1 and Node2 > 2.Submit a sample mapreduce on default queue which will stay in ACCEPTED > state > 3.Change default node label expression for default queue to label2 in > capacity-scheduler.xml > yarn rmadmin -refreshQueues > queue's config gets reflected to label2 as shown on RM UI queue section but > job still stays at ACCEPTED state > 4. Submitting a new job into default queue moves into RUNNING state -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org