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 6B920D6C9 for ; Thu, 1 Nov 2012 16:56:06 +0000 (UTC) Received: (qmail 6458 invoked by uid 500); 1 Nov 2012 16:56:01 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 6338 invoked by uid 500); 1 Nov 2012 16:56:01 -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 6321 invoked by uid 99); 1 Nov 2012 16:56:01 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 16:56:01 +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 harsh@cloudera.com designates 209.85.223.176 as permitted sender) Received: from [209.85.223.176] (HELO mail-ie0-f176.google.com) (209.85.223.176) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Nov 2012 16:55:56 +0000 Received: by mail-ie0-f176.google.com with SMTP id k11so4415434iea.35 for ; Thu, 01 Nov 2012 09:55:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding:x-gm-message-state; bh=/xTBVCfLy3fpQ6p+qG1Qz7E6hYSMABZZg0GHTWvSJrA=; b=iVWPlXW8dAN2aEP3tzRd2wFbSFOJayPwGjsk4Hvq36Wi+tshNGJyyS1xJ6lvLxNXLi epJNefh3Kb7ITFJW8aePmS4cWr3CwVmoIXLjXg1O1pcmVc2aA+o+k/hgqCDtP2+uJrDT LGoXlP5J/7v66ZoxI0fl219zkAxDEfFJcLSzDi7C820jfXET7ldmcObraD+PdrhR9TRw JwzYKPJuaZ7ej2xuxgQLRX0bX0oQZ9bcwr7Onc9nFCkze/JD1cvhag++nh5N+78mb6o/ rOiYs6Nh1QIXatuTyZ9Tf0VjXeJX4D5RzE6HqjwvCdEdrBEepE0JdD7wCsWE0g+ZtOg/ vGQA== Received: by 10.50.197.225 with SMTP id ix1mr1853669igc.66.1351788935931; Thu, 01 Nov 2012 09:55:35 -0700 (PDT) MIME-Version: 1.0 Received: by 10.64.27.8 with HTTP; Thu, 1 Nov 2012 09:55:15 -0700 (PDT) In-Reply-To: References: From: Harsh J Date: Thu, 1 Nov 2012 22:25:15 +0530 Message-ID: Subject: Re: Set the number of maps To: user@hadoop.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQkm5Tf0h0zDsqEv2ftZ/O607BjkDmqLLxAdpp/J0GJ591U9olXH6CU/qaJ+mrcNeKtsBSHA X-Virus-Checked: Checked by ClamAV on apache.org It can't be set from the code this way - the slot property is applied at the TaskTracker service level (as the name goes). Since you're just testing at the moment, try to set these values, restart TTs, and run your jobs again. You do not need to restart JT at any point for tweaking these values. On Thu, Nov 1, 2012 at 7:13 PM, Cogan, Peter (Peter) wrote: > Hi > > I understand that the maximum number of concurrent map tasks is set by > mapred.tasktracker.map.tasks.maximum - however I wish to run with a smal= ler > number of maps (am testing disk IO). I thought that I could set that with= in > the main program using > > conf.set("mapred.tasktracker.map.tasks.maximuma", "4"); > > > to run with 4 maps =96 but that seems to have no impact. I know I could j= ust > change the mapred-site.xml and restart map reduce but that's kind of a pa= in. > Can it be set from within the code? > > > Thanks > > Peter --=20 Harsh J