Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 68181EB61 for ; Wed, 28 Nov 2012 06:10:52 +0000 (UTC) Received: (qmail 35994 invoked by uid 500); 28 Nov 2012 06:10:47 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 35651 invoked by uid 500); 28 Nov 2012 06:10:47 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 35559 invoked by uid 99); 28 Nov 2012 06:10:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 06:10:45 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mogwaing@gmail.com designates 209.85.220.176 as permitted sender) Received: from [209.85.220.176] (HELO mail-vc0-f176.google.com) (209.85.220.176) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 28 Nov 2012 06:10:10 +0000 Received: by mail-vc0-f176.google.com with SMTP id fl13so16201731vcb.35 for ; Tue, 27 Nov 2012 22:09:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ITAJZha5y0dZuWDm/pKHmZqM4vc6nVyYGUsRPRRDtb8=; b=zumoilIr5Hyh2i28Ed2zivv+7sNoQIQUM8al2USaJMZXpfeUCgIzO+Q26CKScBDk1p pHyUPHO3HIGIP+HhBtyvanUys1svJTHVCmpYCE8XaoG7frl4jhtZXkHwhS8kt2xJ4xGo Woc4KDW+4w1wEb4v9P4y1L/P7ZDEzU9Ytd/TOoVsCKBDVOKx90AObBe7QOxKW/0LJ0kh nNfozC2mv/+S/FqZn89P/ewCLd+qyKGe+FQd6bNz9jnUX8QxeS7Vxumk8EOWle8tbz6X /ESCRWHTh5etM4Z5BOBTYDQJ+WTmBjFA7uAVwsMLK4Uu3VO6xNyI++t3xEl1nFCN6NPv fUkA== MIME-Version: 1.0 Received: by 10.220.140.143 with SMTP id i15mr11944862vcu.15.1354082989775; Tue, 27 Nov 2012 22:09:49 -0800 (PST) Received: by 10.58.94.101 with HTTP; Tue, 27 Nov 2012 22:09:49 -0800 (PST) In-Reply-To: References: Date: Wed, 28 Nov 2012 15:09:49 +0900 Message-ID: Subject: Re: Assigning reduce tasks to specific nodes From: Hiroyuki Yamada To: user@hadoop.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Virus-Checked: Checked by ClamAV on apache.org Hi Harsh, Thank you for the information. I understand the current circumstances. How about for mappers ? As far as I tested, location information in InputSplit is ignored in 0.20.2, so there seems no easy way for assigning mappers to specific nodes. (I before checked the source and noticed that location information is not restored when deserializing the InputSplit instance.) Thanks, Hiroyuki On Wed, Nov 28, 2012 at 2:08 PM, Harsh J wrote: > This is not supported/available currently even in MR2, but take a look at > https://issues.apache.org/jira/browse/MAPREDUCE-199. > > > On Wed, Nov 28, 2012 at 9:34 AM, Hiroyuki Yamada wrote: >> >> Hi, >> >> I am wondering how I can assign reduce tasks to specific nodes. >> What I want to do is, for example, assigning reducer which produces >> part-00000 to node xxx000, >> and part-00001 to node xxx001 and so on. >> >> I think it's abount task assignment scheduling but >> I am not sure where to customize to achieve this. >> Is this done by writing some extensions ? >> or any easier way to do this ? >> >> Regards, >> Hiroyuki > > > > > -- > Harsh J