[
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.201409242210.txt
[~leftnoteasy],
I'm sorry for the churn on patches, and thanks again for helping me on this.
The current patch maintains the existing behavior as before, and addresses the
concern you raised in comment:
https://issues.apache.org/jira/browse/YARN-2056?focusedCommentId=14142404&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14142404
That is, it addresses the case where
{code}
root has A,B,C, total capacity = 90
A.guaranteed = 30, A.pending = 20, A.current = 40
B.guaranteed = 30, B.pending = 0, B.current = 50
C.guaranteed = 30, C.pending = 0, C.current = 0
{code}
It will levelize the over-capacity queues to be A.idealAssigned = 45,
B.idealAssigned = 45
This patch implements the algorithm I described in comment:
https://issues.apache.org/jira/browse/YARN-2056?focusedCommentId=14145650&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14145650
> 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,
> YARN-2056.201409232329.txt, YARN-2056.201409242210.txt
>
>
> We need to be able to disable preemption at individual queue level
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
