Return-Path: 
 <user-return-15594-apmail-hadoop-mapreduce-user-archive=hadoop.apache.org@hadoop.apache.org>
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 A6F2410601
	for <apmail-hadoop-mapreduce-user-archive@minotaur.apache.org>;
 Sat, 31 May 2014 05:12:48 +0000 (UTC)
Received: (qmail 97262 invoked by uid 500); 31 May 2014 01:04:44 -0000
Delivered-To: apmail-hadoop-mapreduce-user-archive@hadoop.apache.org
Received: (qmail 97160 invoked by uid 500); 31 May 2014 01:04:44 -0000
Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:user-help@hadoop.apache.org>
List-Unsubscribe: <mailto:user-unsubscribe@hadoop.apache.org>
List-Post: <mailto:user@hadoop.apache.org>
List-Id: <user.hadoop.apache.org>
Reply-To: user@hadoop.apache.org
Delivered-To: mailing list user@hadoop.apache.org
Received: (qmail 97153 invoked by uid 99); 31 May 2014 01:04:44 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 May 2014 01:04:44 +0000
X-ASF-Spam-Status: No, hits=1.5 required=5.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of athomewithagroovebox@gmail.com
 designates 74.125.82.180 as permitted sender)
Received: from [74.125.82.180] (HELO mail-we0-f180.google.com) (74.125.82.180)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 31 May 2014 01:04:41 +0000
Received: by mail-we0-f180.google.com with SMTP id q58so2802066wes.11
        for <user@hadoop.apache.org>; Fri, 30 May 2014 18:04:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to:content-type;
        bh=TDSGvA2rM2aTDXdvljQkX4KUIlSej17DDePoWutyPIg=;
        b=PKWHvsCj+WDoiChaQEwiAXdfYFJovTafHQgyd/bZ7PV4p8oa96LAJYtfI2h+RjZsmg
         YcPFaMZTA1arG2CU4DzVrYhfNPAff0Siduh8FY0DvYsdpMhJNgusqi6RlFR31Eq8CRMS
         VgsGOQihzPCYuSGdW55oFm5d2RAjCoQmuShzzBIxvBtFBaYUjr473Bb4zsHlksOr/COL
         Yx5BGLg7jW/CjxP+4AUn49YeEwIiADgf8a297Gj9C3oY1Yqk23mF8SI7UbeurF0eBAAZ
         aACJPJV+RaNIYYr7XzvhL4QolcCWAkJXkdrQjSjfMeznhga4am84gQv0el8Xxn+KemeZ
         t1xQ==
X-Received: by 10.180.73.66 with SMTP id j2mr1604123wiv.36.1401498257891; Fri,
 30 May 2014 18:04:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.216.202.71 with HTTP; Fri, 30 May 2014 18:03:57 -0700 (PDT)
From: jeremy p <athomewithagroovebox@gmail.com>
Date: Fri, 30 May 2014 18:03:57 -0700
Message-ID: 
 <CAKjW-3+vANMQkMBoyKG--xanLb6vXgrtYFnLfOCM2WOJA5-o8w@mail.gmail.com>
Subject: How to set the max mappers per node on a per-job basis?
To: user@hadoop.apache.org
Content-Type: multipart/alternative; boundary=f46d0438921bd0a71404faa7bd61
X-Virus-Checked: Checked by ClamAV on apache.org

--f46d0438921bd0a71404faa7bd61
Content-Type: text/plain; charset=UTF-8

Hello all,

I have two jobs, Job A and Job B.  Job A is not very CPU-intensive, and so
we would like to run it with 50 mappers per node.  Job B is very
CPU-intensive, and so we would like to run it with 25 mappers per node.
 How can we request a different number of mappers per node for each job?

--Jeremy

--f46d0438921bd0a71404faa7bd61
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hello all,<div><br></div><div>I have two jobs, Job A and J=
ob B. =C2=A0Job A is not very CPU-intensive, and so we would like to run it=
 with 50 mappers per node. =C2=A0Job B is very CPU-intensive, and so we wou=
ld like to run it with 25 mappers per node. =C2=A0How can we request a diff=
erent number of mappers per node for each job? =C2=A0</div>

<div><br></div><div>--Jeremy</div></div>

--f46d0438921bd0a71404faa7bd61--