[jira] [Updated] (YARN-3764) CapacityScheduler forbid of moving LeafQueue from one parent to another

2015-06-03 Thread Wangda Tan (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wangda Tan updated YARN-3764:
-
Description: 
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)
  /  \
 xy
(50)  (100)
{code}

We should forbid admin doing that.


  was:
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)
  /  \
 xy
(50)  (100)
{code}

We should handle this case better.



> CapacityScheduler forbid of 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)
>   /  \
>  xy
> (50)  (100)
> {code}
> We should forbid admin doing that.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)


[jira] [Updated] (YARN-3764) CapacityScheduler forbid of moving LeafQueue from one parent to another

2015-06-03 Thread Wangda Tan (JIRA)

 [ 
https://issues.apache.org/jira/browse/YARN-3764?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Wangda Tan updated YARN-3764:
-
Summary: CapacityScheduler forbid of moving LeafQueue from one parent to 
another  (was: CapacityScheduler should properly handle moving LeafQueue from 
one parent to another)

> CapacityScheduler forbid of 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)
>   /  \
>  xy
> (50)  (100)
> {code}
> We should handle this case better.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)