[
https://issues.apache.org/jira/browse/YARN-9925?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhu Joseph updated YARN-9925:
--------------------------------
Description:
CapacitySchedulerQueueManager allows unsupported Queue hierarchy. When creating
a queue with same name as an existing parent queue name - it has to fail with
below.
{code:java}
Caused by: java.io.IOException: A is moved from:root.A to:root.B.A after
refresh, which is not allowed.Caused by: java.io.IOException: A is moved
from:root.A to:root.B.A after refresh, which is not allowed. at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerQueueManager.validateQueueHierarchy(CapacitySchedulerQueueManager.java:335)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerQueueManager.reinitializeQueues(CapacitySchedulerQueueManager.java:180)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitializeQueues(CapacityScheduler.java:762)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:473)
... 70 more
{code}
In Some cases, the error is not thrown while creating the queue but thrown at
submission of job "Failed to submit application_1571677375269_0002 to YARN :
Application application_1571677375269_0002 submitted by user : systest to
non-leaf queue : B"
Below scenarios are allowed but it should not
{code:java}
It allows root.A.A1.B when root.B.B1 exists already.
1. Add root.A
2. Add root.A.A1
3. Add root.B
4. Add root.B.B1
5. Allows Add of root.A.A1.B
It allows two root queues:
1. Add root.A
2. Add root.B
3. Add root.A.A1
4. Allows Add of root.A.A1.root
{code}
Below scenario is handled properly:
{code:java}
It does not allow root.B.A when root.A.A1 exists already.
1. Add root.A
2. Add root.B
3. Add root.A.A1
4. Does not Allow Add of root.B.A
{code}
This error handling has to be consistent in all scenarios.
was:
CapacitySchedulerQueueManager allows unsupported Queue hierarchy. When creating
a queue with same name as an existing parent queue name - it has to fail with
below.
{code:java}
Caused by: java.io.IOException: A is moved from:root.A to:root.B.A after
refresh, which is not allowed.Caused by: java.io.IOException: A is moved
from:root.A to:root.B.A after refresh, which is not allowed. at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerQueueManager.validateQueueHierarchy(CapacitySchedulerQueueManager.java:335)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerQueueManager.reinitializeQueues(CapacitySchedulerQueueManager.java:180)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitializeQueues(CapacityScheduler.java:762)
at
org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:473)
... 70 more
{code}
In Some cases, the error is not thrown while creating the queue but thrown at
submission of job "Failed to submit application_1571677375269_0002 to YARN :
Application application_1571677375269_0002 submitted by user : systest to
non-leaf queue : B"
Below scenarios are allowed but it should not
{code}
1. It allows root.A.A1.B when root.B.B1 exists already.
1. Add root.A
2. Add root.A.A1
3. Add root.B
4. Add root.B.B1
5. Allows Add of root.A.A1.B
2. It allows two root queues:
1. Add root.A
2. Add root.B
3. Add root.A.A1
4. Allows Add of root.A.A1.root
{code}
Below scenario is handled properly:
{code}
1. It does not allow root.B.A when root.A.A1 exists already.
1. Add root.A
2. Add root.B
3. Add root.A.A1
4. Does not Allow Add of root.B.A
{code}
This error handling has to be consistent in all scenarios.
> CapacitySchedulerQueueManager allows unsupported Queue hierarchy
> ----------------------------------------------------------------
>
> Key: YARN-9925
> URL: https://issues.apache.org/jira/browse/YARN-9925
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
>
> CapacitySchedulerQueueManager allows unsupported Queue hierarchy. When
> creating a queue with same name as an existing parent queue name - it has to
> fail with below.
> {code:java}
> Caused by: java.io.IOException: A is moved from:root.A to:root.B.A after
> refresh, which is not allowed.Caused by: java.io.IOException: A is moved
> from:root.A to:root.B.A after refresh, which is not allowed. at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerQueueManager.validateQueueHierarchy(CapacitySchedulerQueueManager.java:335)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacitySchedulerQueueManager.reinitializeQueues(CapacitySchedulerQueueManager.java:180)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitializeQueues(CapacityScheduler.java:762)
> at
> org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.reinitialize(CapacityScheduler.java:473)
> ... 70 more
> {code}
> In Some cases, the error is not thrown while creating the queue but thrown at
> submission of job "Failed to submit application_1571677375269_0002 to YARN :
> Application application_1571677375269_0002 submitted by user : systest to
> non-leaf queue : B"
> Below scenarios are allowed but it should not
> {code:java}
> It allows root.A.A1.B when root.B.B1 exists already.
>
> 1. Add root.A
> 2. Add root.A.A1
> 3. Add root.B
> 4. Add root.B.B1
> 5. Allows Add of root.A.A1.B
> It allows two root queues:
>
> 1. Add root.A
> 2. Add root.B
> 3. Add root.A.A1
> 4. Allows Add of root.A.A1.root
>
> {code}
> Below scenario is handled properly:
> {code:java}
> It does not allow root.B.A when root.A.A1 exists already.
>
> 1. Add root.A
> 2. Add root.B
> 3. Add root.A.A1
> 4. Does not Allow Add of root.B.A
> {code}
> This error handling has to be consistent in all scenarios.
--
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
