You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2013/07/15 20:45:15 UTC
[jira] [Commented] (MAPREDUCE-4305) Implement delay scheduling in
capacity scheduler for improving data locality
[ https://issues.apache.org/jira/browse/MAPREDUCE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708799#comment-13708799 ]
Karthik Kambatla commented on MAPREDUCE-4305:
---------------------------------------------
Mayank's latest patch looks good. [~acmurthy], do you have any further comments on this?
> Implement delay scheduling in capacity scheduler for improving data locality
> ----------------------------------------------------------------------------
>
> Key: MAPREDUCE-4305
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-4305
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Mayank Bansal
> Assignee: Mayank Bansal
> Attachments: MAPREDUCE-4305, MAPREDUCE-4305-1.patch, PATCH-MAPREDUCE-4305-MR1-1.patch, PATCH-MAPREDUCE-4305-MR1-2.patch, PATCH-MAPREDUCE-4305-MR1-3.patch, PATCH-MAPREDUCE-4305-MR1-6.patch, PATCH-MAPREDUCE-4305-MR1-7.patch, PATCH-MAPREDUCE-4305-MR1.patch
>
>
> Capacity Scheduler data local tasks are about 40%-50% which is not good.
> While my test with 70 node cluster i consistently get data locality around 40-50% on a free cluster.
> I think we need to implement something like delay scheduling in the capacity scheduler for improving the data locality.
> http://radlab.cs.berkeley.edu/publication/308
> After implementing the delay scheduling on Hadoop 22 I am getting 100 % data locality in free cluster and around 90% data locality in busy cluster.
> Thanks,
> Mayank
--
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