hadoop-yarn-issues mailing list archives

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

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

Harsh J commented on YARN-80:

Hi Arun,

Thanks very much for doing this! We could probably address this in a new JIRA but I had two

- Why was the feature decided to be disabled by default?
- Is there no way to not have people change configuration based on their # of racks (i.e.
make it automated)?
> 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
>            Assignee: Arun C Murthy
>             Fix For: 2.0.2-alpha
>         Attachments: YARN-80.patch, YARN-80.patch
> 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