[
https://issues.apache.org/jira/browse/YARN-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14574381#comment-14574381
]
Hudson commented on YARN-3764:
------------------------------
SUCCESS: Integrated in Hadoop-Yarn-trunk #949 (See
[https://builds.apache.org/job/Hadoop-Yarn-trunk/949/])
YARN-3764. CapacityScheduler should forbid moving LeafQueue from one parent to
another. Contributed by Wangda Tan (jianhe: rev
6ad4e59cfc111a92747fdb1fb99cc6378044832a)
* hadoop-yarn-project/CHANGES.txt
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestQueueParsing.java
*
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java
> CapacityScheduler should forbid 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
> Fix For: 2.7.1
>
> Attachments: YARN-3764.1.patch
>
>
> 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 forbid admin doing that.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
