[ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15872667#comment-15872667
]
Hudson commented on YARN-6193:
------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #11276 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/11276/])
YARN-6193. FairScheduler might not trigger preemption when using DRF. (kasha: rev dbbfcf74ab44d7bfdc805b63affd0defc57182b8)
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/FSAppAttempt.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/fair/TestFairSchedulerPreemption.java
> FairScheduler might not trigger preemption when using DRF
> ---------------------------------------------------------
>
> Key: YARN-6193
> URL: https://issues.apache.org/jira/browse/YARN-6193
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: fairscheduler
> Affects Versions: 2.8.0
> Reporter: Karthik Kambatla
> Assignee: Karthik Kambatla
> Attachments: YARN-6193.000.patch, YARN-6193.001.patch, YARN-6193.002.patch, YARN-6193.003.patch
>
>
> {{FSAppAttempt#canContainerBePreempted}} verifies preempting a container doesn't lead
to new starvation ({{Resources.fitsIn}}). When using DRF, this leads to verifying both resources
instead of just the dominant resource. Ideally, the check should be based on policy.
> Note that current implementation of {{DominantResourceFairnessPolicy#checkIfUsageOverFairShare}}
is broken.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org
|