You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2017/02/15 05:54:41 UTC

[jira] [Commented] (YARN-6193) FairScheduler might not trigger preemption when using DRF

    [ https://issues.apache.org/jira/browse/YARN-6193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15867309#comment-15867309 ] 

Karthik Kambatla commented on YARN-6193:
----------------------------------------

Patch that:
# Uses policy-based check instead of fitsIn to see if a container can be preempted
# Move some of the SchedulingPolicy methods to the abstract base class instead of sub-classes
# Augmented tests to consider DRF for both minshare and fairshare preemption

> 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: Bug
>          Components: fairscheduler
>    Affects Versions: 2.8.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>         Attachments: YARN-6193.000.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