Eric Payne commented on YARN-2056:

[~leftnoteasy]: Good catch! It's actually even worse than what you specified. 
The way the patch is written now, if the disable preemption queue is 1) over 
capacity and 2) asking for more resources, it will preempt from other queues 
and make them go below their guarantee!

I don't have a good suggestion to fix the problem you have outlined other than 
stating the following:
If a queue is over capacity and has untouchable resources in its pool, it 
cannot preempt other queues at that level. In other words, if you disable 
preemption on a queue, the only way it will get over it's capacity is when 
other resources free up. Those other resources won't be preempted to fulfill a 
non-preemptable queues request if that non-preemptable queue is already over 

> Disable preemption at Queue level
> ---------------------------------
>                 Key: YARN-2056
>                 URL: https://issues.apache.org/jira/browse/YARN-2056
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>    Affects Versions: 2.4.0
>            Reporter: Mayank Bansal
>            Assignee: Eric Payne
>         Attachments: YARN-2056.201408202039.txt, YARN-2056.201408260128.txt, 
> YARN-2056.201408310117.txt, YARN-2056.201409022208.txt, 
> YARN-2056.201409181916.txt, YARN-2056.201409210049.txt
> We need to be able to disable preemption at individual queue level

This message was sent by Atlassian JIRA

Reply via email to