[
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.201411142002.txt
[~leftnoteasy], Thank you for all of your help. Uploading new patch.
bq. Instead of multiply you should use multiplyAndNormalizeUp here.
Using {{multiplyAndNormalizeUp}} helps. However, for the use case in
{{testHierarchicalLarge}}, the rounding is still different with the new
algorithm (7 and 5 instead of 9 and 4).
bq. Actually I think we should consider minimum_allocation in preemption
policy, we can address that in a separated JIRA.
Would you please create a new JIRA and elaborate on this further?
{quote}
bq. {{testDisablePreemptionOverCapPlusPending}}
Since the result is not changed before/after we set preemption queue, I think
it is unnecessary, I would suggest to take it out.
{quote}
I removed this test.
> 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,
> YARN-2056.201410132225.txt, YARN-2056.201410141330.txt,
> YARN-2056.201410232244.txt, YARN-2056.201410311746.txt,
> YARN-2056.201411041635.txt, YARN-2056.201411072153.txt,
> YARN-2056.201411122305.txt, YARN-2056.201411132215.txt,
> YARN-2056.201411142002.txt
>
>
> We need to be able to disable preemption at individual queue level
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
