[
https://issues.apache.org/jira/browse/YARN-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998174#comment-13998174
]
Hudson commented on YARN-1957:
------------------------------
FAILURE: Integrated in Hadoop-Mapreduce-trunk #1779 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1779/])
YARN-1957. Consider the max capacity of the queue when computing the ideal
capacity for preemption. Contributed by Carlo Curino (cdouglas:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1594414)
* /hadoop/common/trunk/hadoop-yarn-project/CHANGES.txt
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/monitor/capacity/ProportionalCapacityPreemptionPolicy.java
*
/hadoop/common/trunk/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/monitor/capacity/TestProportionalCapacityPreemptionPolicy.java
> ProportionalCapacitPreemptionPolicy handling of corner cases...
> ---------------------------------------------------------------
>
> Key: YARN-1957
> URL: https://issues.apache.org/jira/browse/YARN-1957
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: resourcemanager
> Affects Versions: 2.4.0
> Reporter: Carlo Curino
> Assignee: Carlo Curino
> Labels: capacity-scheduler, preemption
> Fix For: 3.0.0, 2.5.0, 2.4.1
>
> Attachments: YARN-1957.patch, YARN-1957.patch, YARN-1957_test.patch
>
>
> The current version of ProportionalCapacityPreemptionPolicy should be
> improved to deal with the following two scenarios:
> 1) when rebalancing over-capacity allocations, it potentially preempts
> without considering the maxCapacity constraints of a queue (i.e., preempting
> possibly more than strictly necessary)
> 2) a zero capacity queue is preempted even if there is no demand (coherent
> with old use of zero-capacity to disabled queues)
> The proposed patch fixes both issues, and introduce few new test cases.
--
This message was sent by Atlassian JIRA
(v6.2#6252)