[
https://issues.apache.org/jira/browse/YARN-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571479#comment-14571479
]
Vinod Kumar Vavilapalli commented on YARN-3764:
-----------------------------------------------
bq. A short term fix is don't allow remove queue under parentQueue.
We never supported removing queues. So this is not just a short-term fix, this
is the right fix for now.
> CapacityScheduler should properly handle moving LeafQueue from one parent to
> another
> ------------------------------------------------------------------------------------
>
> Key: YARN-3764
> URL: https://issues.apache.org/jira/browse/YARN-3764
> Project: Hadoop YARN
> Issue Type: Bug
> Reporter: Wangda Tan
> Assignee: Wangda Tan
> Priority: Blocker
>
> Currently CapacityScheduler doesn't handle the case well, for example:
> A queue structure:
> {code}
> root
> |
> a (100)
> / \
> x y
> (50) (50)
> {code}
> And reinitialize using following structure:
> {code}
> root
> / \
> (50)a x (50)
> |
> y
> (100)
> {code}
> The actual queue structure after reinitialize is:
> {code}
> root
> / \
> a (50) x (50)
> / \
> x y
> (50) (100)
> {code}
> We should handle this case better.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
