[ 
https://issues.apache.org/jira/browse/YARN-9849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17106901#comment-17106901
 ] 

Bilwa S T commented on YARN-9849:
---------------------------------

cc [~inigoiri]

> Leaf queues not inheriting parent queue status after adding status as 
> “RUNNING” and thereafter, commenting the same in capacity-scheduler.xml 
> ----------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: YARN-9849
>                 URL: https://issues.apache.org/jira/browse/YARN-9849
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacity scheduler
>            Reporter: Sushanta Sen
>            Assignee: Bilwa S T
>            Priority: Major
>         Attachments: YARN-9849.001.patch, YARN-9849.002.patch, 
> YARN-9849.003.patch
>
>
> 【Precondition】:
> 1. Install the cluster
> 2. Config Queues with more numbers say 2 parent [default,q1] & 4 leaf [q2,q3]
> 3. Cluster should be up and running
> 【Test step】:
> 1.By default leaf quques inherit parent status 
> 2.Change leaf queues status  as "RUNNING" explicitly
> 3. Run refresh command, leaf queues status shown as "RUNNING" in CLI/UI
> 4. Therafter,change the leaft queues status to "STOPPED"  and refresh command
> 5. Run refresh command, leaf queues status shown as "STOPPING" in CLI/UI
> 6. Now comment the leafy queues status and run refresh queues
> 7.Observe
> 【Expect Output】:
> The leaf queues status should be displayed as "RUNNING" inheriting from the 
> parent queue.
> 【Actual Output】:
> Still displays the leaf queues status as "STOPPED" raather than inheriting 
> the same from parent which is in RUNNING



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org

Reply via email to