[
https://issues.apache.org/jira/browse/YARN-2056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14108210#comment-14108210
]
Eric Payne commented on YARN-2056:
----------------------------------
[~leftnoteasy],
Thank you for your suggestion.
I tried implementing a {{DisablePreempt}} value in 2 separate ways:
# Inn the {{cloneQueue}} method, the implementation did not create a TempQueue
if it was over capacity and the {{DisablePreempt}} property is set.
# In the {{computeFixpointAllocation}} method, the implementation takes the
Tempqueue out of the list if it is over capacity and the {{DisablePreempt}}
iproperty is set.
In either case, it did not preempt containers on the specified queue. However,
it did not preempt containers from the other over-capacity queues, either.
Please let me know if you have suggestions about how to better implement this
to get the desired behavior.
I think that the existing patch may be the best compromise, since it does
provide the desired functionality, and it also gives the administrator a little
more flexibility in tuning preemption.
> 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
>
>
> We need to be able to disable preemption at individual queue level
--
This message was sent by Atlassian JIRA
(v6.2#6252)
