Return-Path: X-Original-To: apmail-hadoop-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-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 689B4FF3B for ; Mon, 15 Apr 2013 18:08:41 +0000 (UTC) Received: (qmail 36951 invoked by uid 500); 15 Apr 2013 18:08:36 -0000 Delivered-To: apmail-hadoop-user-archive@hadoop.apache.org Received: (qmail 36854 invoked by uid 500); 15 Apr 2013 18:08:36 -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 36844 invoked by uid 99); 15 Apr 2013 18:08:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Apr 2013 18:08:36 +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 amalgjos@gmail.com designates 209.85.223.181 as permitted sender) Received: from [209.85.223.181] (HELO mail-ie0-f181.google.com) (209.85.223.181) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Apr 2013 18:08:31 +0000 Received: by mail-ie0-f181.google.com with SMTP id as1so1692050iec.40 for ; Mon, 15 Apr 2013 11:08:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=PMuAN4krHD/xxQOUL1xd7aR6uaafNaxqcND4LCiAHfo=; b=nlFikdcu4b5p+VbETIxXnmHuBjVjczYn9BEHrYbS7TnLtiheNbzmEot0Se54dO6tCP E+xQoVpmhG6QF6uiDSXdYVSjhfsphSuigYVyYzdP5+FED2DLvi/9HcxdV/KeFa+7gYRm bRzEuA38bMjDXX/LSrtvuFMxSp7xn1s9lYy4Vavjt2eRgEDzbD8S3hAvOjSS+bXLMBQv lE0lMV+SFFzt4Q5V0qxlRo/g30CCdFXml9RnHGCI+AHYxXiX5ySovFHqUx/0Di7JQxzY xHQYD91wrwxOchbJfr4BsubcZp6zEm0rGDblCeTGjcDJsR6h7Q+Vezl2wyVfj+BjTEHF pLYg== MIME-Version: 1.0 X-Received: by 10.50.140.5 with SMTP id rc5mr5908359igb.78.1366049290027; Mon, 15 Apr 2013 11:08:10 -0700 (PDT) Received: by 10.64.16.197 with HTTP; Mon, 15 Apr 2013 11:08:09 -0700 (PDT) In-Reply-To: <516BE036.5090807@buscapecompany.com> References: <516BE036.5090807@buscapecompany.com> Date: Mon, 15 Apr 2013 23:38:09 +0530 Message-ID: Subject: Re: Adjusting tasktracker heap size? From: Amal G Jose To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=e89a8f83a34bad868504da6a225b X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f83a34bad868504da6a225b Content-Type: text/plain; charset=ISO-8859-1 It depends on the type of job that is frequently submitting. RAM size of the machine. Heap size of tasktracker= (mapslots+reduceslots)*jvm size We can adjust this according to our requirement to fine tune our cluster. This is my thought. On Mon, Apr 15, 2013 at 4:40 PM, MARCOS MEDRADO RUBINELLI < marcosm@buscapecompany.com> wrote: > Hi, > > I am currently tuning a cluster, and I haven't found much information on > what factors to consider while adjusting the heap size of tasktrackers. > Is it a direct multiple of the number of map+reduce slots? Is there > anything else I should consider? > > Thank you, > Marcos --e89a8f83a34bad868504da6a225b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It depends on the type of job that is frequently submittin= g.
RAM size of the machine.
Heap size of tasktrac= ker=3D (mapslots+reduceslots)*jvm size
We can adjust this a= ccording to our requirement to fine tune our cluster.
This is my thought.

On Mon, Apr 15, 2013 at 4:40 PM, MARCOS MEDRAD= O RUBINELLI <marcosm@buscapecompany.com> wrote:
Hi,

I am currently tuning a cluster, and I haven't found much information o= n
what factors to consider while adjusting the heap size of tasktrackers.
Is it a direct multiple of the number of map+reduce slots? Is there
anything else I should consider?

Thank you,
Marcos

--e89a8f83a34bad868504da6a225b--