Return-Path: X-Original-To: apmail-hadoop-mapreduce-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 73D3CE727 for ; Mon, 11 Feb 2013 11:55:09 +0000 (UTC) Received: (qmail 65688 invoked by uid 500); 11 Feb 2013 11:55:04 -0000 Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org Received: (qmail 65347 invoked by uid 500); 11 Feb 2013 11:55: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 65328 invoked by uid 99); 11 Feb 2013 11:55:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 11:55:00 +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.172 as permitted sender) Received: from [209.85.223.172] (HELO mail-ie0-f172.google.com) (209.85.223.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 11 Feb 2013 11:54:54 +0000 Received: by mail-ie0-f172.google.com with SMTP id c10so7414346ieb.17 for ; Mon, 11 Feb 2013 03:54:33 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=pZHWP0pJVEH+ptup3ce7EfqmqYAPpNTk2MdfqGFKcvE=; b=gCTcHluV86gLF7t9bY1QwziBZzp0olEgrIM3puWfN2NpEJ5t94MUFxRBBCNZeSNjF+ f16ZhJNpSvQcZPKdDPrKW68GPwhd/neMAADgylfPweRHIZ+MYznL8Pxgja0hISRhvrFz p31m7doVClc/lLEqVH4zHcHFyMgI5eAJ0wIRtLjynqY6b3kB3neQZEBWl4Esh2gD7Jj0 Vu0miWkD3SKhT0DkwvVfrcAVCRU5hNL8Yc8DGp3koxoRqzLy1sqRmSgkbBJnEkeuvQNG LV9lZ8R2ELT7YNk7uYksT8/RZabCVfjbh4vDe0/esS0pF7d5p8YogP6I1/eQ5VDEIrtv YF1A== X-Received: by 10.50.45.197 with SMTP id p5mr11431473igm.41.1360583673570; Mon, 11 Feb 2013 03:54:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.50.91.161 with HTTP; Mon, 11 Feb 2013 03:54:13 -0800 (PST) In-Reply-To: References: From: Harsh J Date: Mon, 11 Feb 2013 17:24:13 +0530 Message-ID: Subject: Re: max number of map/reduce per node To: "" Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQkRl1dUSFDN+2zv31AgQbHlPhTOJ5qG+Qov6ci3R0eOnHi7XTIR/WZFHz8krGkX+lz1R2md X-Virus-Checked: Checked by ClamAV on apache.org Hi, My reply inline. On Mon, Feb 11, 2013 at 5:15 PM, Oleg Ruchovets wrote: > Hi > I found that my job runs with such parameters: > mapred.tasktracker.map.tasks.maximum 4 > mapred.tasktracker.reduce.tasks.maximum 2 > > I try to change these parameters from my java code > > Properties properties = new Properties(); > properties.put("mapred.tasktracker.map.tasks.maximum" , "8"); > properties.put("mapred.tasktracker.reduce.tasks.maximum" , "4"); These properties are a per-tasktracker configuration, not applicable or read from clients. Also, if you're tweaking client-end properties, using the Java Properties class is not the right way to go about it. See Configuration API: http://hadoop.apache.org/common/docs/current/api/org/apache/hadoop/conf/Configuration.html > But executing the job I didn't get updated values of these parameters , it > remains: > > mapred.tasktracker.map.tasks.maximum 4 > mapred.tasktracker.reduce.tasks.maximum 2 > > > Should I change the parameters on hadoop XML configuration files? Yes, as these are per *tasktracker* properties, not client ones. > Please advice. > > > > > > -- Harsh J