hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carlo Curino (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-567) RM changes to support preemption for FairScheduler and CapacityScheduler
Date Thu, 09 May 2013 21:25:17 GMT

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

Carlo Curino resolved YARN-567.

       Resolution: Fixed
    Fix Version/s: 2.0.5-beta

Fixed as part of YARN-568
> RM changes to support preemption for FairScheduler and CapacityScheduler
> ------------------------------------------------------------------------
>                 Key: YARN-567
>                 URL: https://issues.apache.org/jira/browse/YARN-567
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: resourcemanager
>            Reporter: Carlo Curino
>            Assignee: Carlo Curino
>             Fix For: 2.0.5-beta
>         Attachments: YARN-567.patch, YARN-567.patch
> A common tradeoff in scheduling jobs is between keeping the cluster busy and enforcing
capacity/fairness properties. FairScheduler and CapacityScheduler takes opposite stance on
how to achieve this. 
> The FairScheduler, leverages task-killing to quickly reclaim resources from currently
running jobs and redistributing them among new jobs, thus keeping the cluster busy but waste
useful work. The CapacityScheduler is typically tuned
> to limit the portion of the cluster used by each queue so that the likelihood of violating
capacity is low, thus never wasting work, but risking to keep the cluster underutilized or
have jobs waiting to obtain their rightful capacity. 
> By introducing the notion of a work-preserving preemption we can remove this tradeoff.
 This requires a protocol for preemption (YARN-45), and ApplicationMasters that can answer
to preemption  efficiently (e.g., by saving their intermediate state, this will be posted
for MapReduce in a separate JIRA soon), together with a scheduler that can issues preemption
requests (discussed in separate JIRAs YARN-568 and YARN-569).
> The changes we track with this JIRA are common to FairScheduler and CapacityScheduler,
and are mostly propagation of preemption decisions through the ApplicationMastersService.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message