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 2016/03/02 02:34:18 UTC

[jira] [Updated] (YARN-3902) Fair scheduler preempts ApplicationMaster

     [ https://issues.apache.org/jira/browse/YARN-3902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla updated YARN-3902:
-----------------------------------
    Issue Type: Sub-task  (was: Bug)
        Parent: YARN-4752

> Fair scheduler preempts ApplicationMaster
> -----------------------------------------
>
>                 Key: YARN-3902
>                 URL: https://issues.apache.org/jira/browse/YARN-3902
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: fairscheduler
>    Affects Versions: 2.3.0
>         Environment: 3.16.0-0.bpo.4-amd64 #1 SMP Debian 3.16.7-ckt2-1~bpo70+1 (2014-12-08) x86_64
>            Reporter: He Tianyi
>            Assignee: He Tianyi
>   Original Estimate: 72h
>  Remaining Estimate: 72h
>
> YARN-2022 have fixed the similar issue related to CapacityScheduler.
> However, FairScheduler still suffer, preempting AM while other normal containers running out there.
> I think we should take the same approach, avoid AM being preempted unless there is no container running other than AM.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)