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 535ABD698 for ; Mon, 27 Aug 2012 17:12:38 +0000 (UTC) Received: (qmail 5972 invoked by uid 500); 27 Aug 2012 17:12:33 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 5880 invoked by uid 500); 27 Aug 2012 17:12:33 -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 5873 invoked by uid 99); 27 Aug 2012 17:12:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2012 17:12:33 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=FSL_RCVD_USER,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of e.v.skaley@gmail.com designates 209.85.214.48 as permitted sender) Received: from [209.85.214.48] (HELO mail-bk0-f48.google.com) (209.85.214.48) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Aug 2012 17:12:25 +0000 Received: by bkty5 with SMTP id y5so1408717bkt.35 for ; Mon, 27 Aug 2012 10:12:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding; bh=NS/k9B/u3r9h0VVh6GZ9kOoP3UW9igFugbKMIQnhtqU=; b=tpkEAK+MmwZokjZdmIKpcv0zydQbBK047U0jagIOM0E7O3OEXiArcAaKZ/nYLaCEFH ovckpq4kemILa/71gS7lYqVLfG+F1lptlvrhsGRuaM6Fh/1uCuz0llPc86618BerI65/ aPp3KyPap8nI/dSzJgaOLzxTSY+boa+nd+KbfqHAVq57fxFf4nGuwU9lucDOUZ48bGOm v1usC+IuEBeQHbv91HVml48n3mughB5cq2wb+vwQ6Pi0YHfUH+CcNz7vp1GkAi/bQRDz 1xhFAVfc1UTeZcvkGs9iWHNxwMxO2ydSFPKisDF9O7fetTKWLVwZ1acCCh7rw0i7MHJp rzTA== Received: by 10.204.154.211 with SMTP id p19mr4179561bkw.12.1346087524638; Mon, 27 Aug 2012 10:12:04 -0700 (PDT) Received: from [192.168.178.27] (port-92-203-2-118.dynamic.qsc.de. [92.203.2.118]) by mx.google.com with ESMTPS id m9sm11099478bkm.10.2012.08.27.10.12.03 (version=SSLv3 cipher=OTHER); Mon, 27 Aug 2012 10:12:04 -0700 (PDT) Message-ID: <503BAA39.9070607@gmail.com> Date: Mon, 27 Aug 2012 19:11:21 +0200 From: Eduard Skaley User-Agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.5) Gecko/20120705 Thunderbird/10.0.5 MIME-Version: 1.0 To: user@hadoop.apache.org Subject: Controlling on which node a reducer will be executed Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi, i have a question concerning the execution of reducers. To use effectively the data locality of blocks in my use case i want to control on which node a reducer will be executed. In my scenario i have a chain of map-reduce jobs where each job will be executed by exactly N reducers. I want to achieve that for each job reducer 1 is executed on node 1, reducer 2 on node 2 and so on. Is it possible with a customization of the BlockPlacementPolicy in MRv2 ? Or is there some other way, maybe some indirect ? Or is it impossible ? Thanks for your help. Eduard