hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Arun C Murthy (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (YARN-80) Support delay scheduling for node locality in MR2's capacity scheduler
Date Mon, 03 Sep 2012 09:56:07 GMT

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

Arun C Murthy moved MAPREDUCE-3210 to YARN-80:

          Component/s:     (was: mrv2)
     Target Version/s:   (was: 0.23.0)
    Affects Version/s:     (was: 0.23.0)
                  Key: YARN-80  (was: MAPREDUCE-3210)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)
> Support delay scheduling for node locality in MR2's capacity scheduler
> ----------------------------------------------------------------------
>                 Key: YARN-80
>                 URL: https://issues.apache.org/jira/browse/YARN-80
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: capacityscheduler
>            Reporter: Todd Lipcon
> The capacity scheduler in MR2 doesn't support delay scheduling for achieving node-level
locality. So, jobs exhibit poor data locality even if they have good rack locality. Especially
on clusters where disk throughput is much better than network capacity, this hurts overall
job performance. We should optionally support node-level delay scheduling heuristics similar
to what the fair scheduler implements in MR1.

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