You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Wangda Tan (JIRA)" <ji...@apache.org> on 2015/06/03 20:55:38 UTC
[jira] [Updated] (YARN-3764) CapacityScheduler should forbid moving
LeafQueue from one parent to another
[ https://issues.apache.org/jira/browse/YARN-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wangda Tan updated YARN-3764:
-----------------------------
Summary: CapacityScheduler should forbid moving LeafQueue from one parent to another (was: CapacityScheduler forbid of moving LeafQueue from one parent to another)
> 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
>
> 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)