Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 3EFBAE0FE for ; Wed, 9 Jan 2013 21:04:14 +0000 (UTC) Received: (qmail 91283 invoked by uid 500); 9 Jan 2013 21:04:14 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 91179 invoked by uid 500); 9 Jan 2013 21:04:14 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 91168 invoked by uid 99); 9 Jan 2013 21:04:13 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 09 Jan 2013 21:04:13 +0000 Date: Wed, 9 Jan 2013 21:04:13 +0000 (UTC) From: "Mayank Bansal (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MAPREDUCE-4305) Implement delay scheduling in capacity scheduler for improving data locality MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MAPREDUCE-4305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13548995#comment-13548995 ] Mayank Bansal commented on MAPREDUCE-4305: ------------------------------------------ HI Karthik, There is more to it then YARN-80, Please followup with my previous comments. Its combination of YARN-80 and part of fair scheduler delay scheduling with timeouts. Thanks, Mayank > 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.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