[
https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Payne updated YARN-2056:
-----------------------------
Attachment: YARN-2056.201408260128.txt
[~leftnoteasy],
I think I have what we need with this patch.
In this patch:
- {{cloneQueues}} includes the queue in the TempQueue list even if it is over
capacity and has the disablePreempt flag set, but it marks the queue as
disablePreempt = true
- {{computeIdealResourceDistribution}} then subtracts the {{disablePreempt}}
queue's used resources from the total guaranteed resources and removes the
queue from calculation during ideal resource distribution.
- Then, whenever preemption is being considered after that, the
disablePreemption flag is checked before determining if a queue's resources
should be preempted.
The result is that the pending allocations are taken from the queue's that do
not have the {{disablePreempt}} flag set (if they are also over-capacity)
> 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
>
>
> We need to be able to disable preemption at individual queue level
--
This message was sent by Atlassian JIRA
(v6.2#6252)
