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 971D010B94 for ; Fri, 13 Sep 2013 16:46:51 +0000 (UTC) Received: (qmail 25026 invoked by uid 500); 13 Sep 2013 16:46:46 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 24787 invoked by uid 500); 13 Sep 2013 16:46:46 -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 24780 invoked by uid 99); 13 Sep 2013 16:46:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Sep 2013 16:46:46 +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 rahul.rec.dgp@gmail.com designates 209.85.220.174 as permitted sender) Received: from [209.85.220.174] (HELO mail-vc0-f174.google.com) (209.85.220.174) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 13 Sep 2013 16:46:39 +0000 Received: by mail-vc0-f174.google.com with SMTP id gd11so1136673vcb.33 for ; Fri, 13 Sep 2013 09:46:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=h6HNBmFGnWTc84uO36ZmA3Nk98HoUlhl4E7BDJanKMU=; b=lIio3Y4TZQVodoBYsxOtnMDjgtEzeTpTeLLv4RiUbYICn+0Mce/yHnqpCQpvrQPGNg /jXehw39dewpJTQRv08Ou7jF64xiwVB5A7ctnC2Qx+ayAQsMq/BidaN02SkfyvV1Ynfd RcD9YIwftefqllc3VfPnkLkE8N5jIbuCA3RzerYIjEP7inU+W3URiO4s+09ZUGmU/rd4 /BXgkppTSwf3SG/EwGJjyIHcjYmTMhRdiy38KKBAMwWl9gR5hldpOYyYP0OWxNzjM1u8 10Bd7tYgeEE1pUxKCkVz7kYh9zkJmFXPu7nk3DB9MyvgHZn5NYa9Z3M0n5j4NDaTy7bO x3/w== X-Received: by 10.52.74.100 with SMTP id s4mr1313645vdv.35.1379090779237; Fri, 13 Sep 2013 09:46:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.58.253.228 with HTTP; Fri, 13 Sep 2013 09:45:59 -0700 (PDT) In-Reply-To: References: From: Rahul Bhattacharjee Date: Fri, 13 Sep 2013 22:15:59 +0530 Message-ID: Subject: Re: Map JVMs not being terminated after MAP jobs complettion. To: "user@hadoop.apache.org" Content-Type: multipart/alternative; boundary=bcaec5016625027cd404e646982c X-Virus-Checked: Checked by ClamAV on apache.org --bcaec5016625027cd404e646982c Content-Type: text/plain; charset=UTF-8 After the map task finishes , the VM terminates and all resources are reclaimable. Reduces might start pulling data from completed map tasks much before all the maps are finished. However there is a property using which you can delay the reduce step till all the maps are completed. Rahul On Fri, Sep 13, 2013 at 12:42 PM, Manu Reddy wrote: > Hi, > > I am running a memory intensive task on my cluster. The reducer class > should load more than 2gb into memory. I was running into memory issues as > the Map JVMS were not terminated after the completion of map tasks and > still were holding onto memory. > > Is this normal? What can I do to ensure that my reduce function gets > called only after all the map jvms are down? > > > -- > Manu Reddy, > mobile no: 091-8143405225, > Hyderabad. > --bcaec5016625027cd404e646982c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
After the map task finishes , the VM terminates and= all resources are reclaimable.

Reduces might start pulling data from completed map tasks much before all t= he maps are finished. However there is a property using which you can delay= the reduce step till all the maps are completed.

Rahul


On Fri, Sep 13, 2013 at 12:42 PM, Manu Reddy <= manubharghav@gm= ail.com> wrote:
Hi,

= I am running a memory intensive task on my cluster. The reducer class shoul= d load more than 2gb into memory. I was running into memory issues as the M= ap JVMS were not terminated after the completion of map tasks and still wer= e holding onto memory.

Is this normal? What can I do to ensure that my reduce function g= ets called only after all the map jvms are down?


--
Manu Re= ddy,
mobile no: 091-8143405225,
Hyderabad.

--bcaec5016625027cd404e646982c--