Return-Path: Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: (qmail 94116 invoked from network); 18 Dec 2009 12:25:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Dec 2009 12:25:06 -0000 Received: (qmail 47099 invoked by uid 500); 18 Dec 2009 12:25:03 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 47011 invoked by uid 500); 18 Dec 2009 12:25:03 -0000 Mailing-List: contact common-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: common-user@hadoop.apache.org Delivered-To: mailing list common-user@hadoop.apache.org Received: (qmail 47001 invoked by uid 99); 18 Dec 2009 12:25:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 12:25:03 +0000 X-ASF-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00 X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ives.aerts@gmail.com designates 209.85.222.198 as permitted sender) Received: from [209.85.222.198] (HELO mail-pz0-f198.google.com) (209.85.222.198) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 18 Dec 2009 12:24:56 +0000 Received: by pzk36 with SMTP id 36so2176176pzk.5 for ; Fri, 18 Dec 2009 04:24:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=1AALBPpvnJxFCOUd0zSkDVuPkfnxYIFlY9geQ7H3L8c=; b=Zzc9ebVa6L0kCCsGkV2C15QQByUW/BrrX29hbku1zXxxQrH+l6tqlH9+jJnLTf1QLM aQSPHpyYPTWnq73fkwXMMTpIbnJcue9ST7uhQ6CNPK2vzXgbrXGGrZTP73a7vOui8RbO RRmntgdOwPE/FOZ+Lvz5pGAtunY8AruomuBLs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=hzJ111xovmqLIRrH9+d/5frp1xw3hd3yFMsuXJZ6D7+d/lAge/ca3OuUNVpBB47dny vrAi1U+D7FL94HE+RMnJ85Hd4lkvfAAICoPKomOXjP8Nci1AwYrG17kUDE5C4Gn6GaWO iZYoOh3uNlp55FMBwBMo+bfMGlJnMzwmup2Fc= MIME-Version: 1.0 Sender: ives.aerts@gmail.com Received: by 10.141.130.7 with SMTP id h7mr2672794rvn.279.1261139076043; Fri, 18 Dec 2009 04:24:36 -0800 (PST) In-Reply-To: <3F5C026C-70AC-4BFA-A61F-6B566F0279E4@apache.org> References: <976b682b0912170206qc06e283me287ee6c69fe4007@mail.gmail.com> <3F5C026C-70AC-4BFA-A61F-6B566F0279E4@apache.org> Date: Fri, 18 Dec 2009 13:24:36 +0100 X-Google-Sender-Auth: de030d5e21943107 Message-ID: <976b682b0912180424l4ef5d705oebeafb9f4777bce8@mail.gmail.com> Subject: Re: Running only node-local jobs From: Ives Aerts To: common-user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 On Thu, Dec 17, 2009 at 8:24 PM, Owen O'Malley wrote: > On Dec 17, 2009, at 2:06 AM, Ives Aerts wrote: ]>> Quick question: is it possible to configure a job such that its map >> tasks will only run node-local? > > No, that is currently not possible without writing your own scheduler. Too bad. Now I wouldn't mind writing my own scheduler (or subclassing an existing one) and plugging it in but I had a quick look and it seems that an important part of the task scheduling logic is actually contained in the JobInProgress class which is instantiated by the JobTracker. So even if I replace the scheduler I won't be able to override that part of the functionality. Or am I missing something? -- Cheers, -Ives