Return-Path: Delivered-To: apmail-hadoop-mapreduce-dev-archive@minotaur.apache.org Received: (qmail 27568 invoked from network); 6 May 2010 19:15:12 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 6 May 2010 19:15:12 -0000 Received: (qmail 91483 invoked by uid 500); 6 May 2010 19:15:12 -0000 Delivered-To: apmail-hadoop-mapreduce-dev-archive@hadoop.apache.org Received: (qmail 91425 invoked by uid 500); 6 May 2010 19:15:12 -0000 Mailing-List: contact mapreduce-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-dev@hadoop.apache.org Delivered-To: mailing list mapreduce-dev@hadoop.apache.org Received: (qmail 91417 invoked by uid 99); 6 May 2010 19:15:12 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 19:15:12 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 May 2010 19:15:10 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o46JEmuL016615 for ; Thu, 6 May 2010 19:14:48 GMT Message-ID: <15104256.15961273173288256.JavaMail.jira@thor> Date: Thu, 6 May 2010 15:14:48 -0400 (EDT) From: "Scott Chen (JIRA)" To: mapreduce-dev@hadoop.apache.org Subject: [jira] Created: (MAPREDUCE-1761) FairScheduler should allow separate configuration of node and rack locality wait time MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org FairScheduler should allow separate configuration of node and rack locality wait time ------------------------------------------------------------------------------------- Key: MAPREDUCE-1761 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1761 Project: Hadoop Map/Reduce Issue Type: Improvement Affects Versions: 0.22.0 Reporter: Scott Chen Assignee: Scott Chen Fix For: 0.22.0 It would be nice that we can separately assign rack locality wait time. In our use case, we would set node locality wait to zero and wait only rack locality. I propose that we add two parameters mapred.fairscheduler.locality.delay.nodetorack mapred.fairscheduler.locality.delay.racktoany This allows specifying the wait time on each stage. And we can use mapred.fairscheduler.locality.delay as the default value of the above fields so that this is backward compatible. Thoughts? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.