Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-user@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of saptarshi.guha@gmail.com
 designates 209.85.200.171 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:reply-to:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=rJcNu/O1HzmQ120pskIiPWVTNFg/c7+di7qtP3dqrzNZnSU+00l5Y62oDbILAvp9fu
         q1EhT9HRXffZ9+SSk9Vg8+Q2n9wvM0Jggypc0bAz8d1p096cT+nfBlNvHAFjfNHcpHzX
         5TPr89gwiptTXyhdcuYR3TNhTCzBhZBgjF/c8=
Message-ID: <1e7471d50812281947k325197beyf424e1bf6c3b6b27@mail.gmail.com>
Date: Sun, 28 Dec 2008 22:47:36 -0500
From: "Saptarshi Guha" <saptarshi.guha@gmail.com>
Reply-To: saptarshi.guha@gmail.com
To: core-user@hadoop.apache.org
Subject: Re: OutofMemory Error, inspite of large amounts provided
In-Reply-To: <1e7471d50812281919i7339c9b0o5eb8fe1a06aa421a@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <1e7471d50812281300t163e7151qb8f7c7fda91f3b8e@mail.gmail.com>
	 <7478CB60-2651-440B-AB8D-6F403C6B9258@cse.unl.edu>
	 <1e7471d50812281919i7339c9b0o5eb8fe1a06aa421a@mail.gmail.com>

Caught it in action.
Running  ps -e -o 'vsz pid ruser args' |sort -nr|head -5
on a machine where the map task was running
04812 16962 sguha    /home/godhuli/custom/jdk1.6.0_11/jre/bin/java
-Djava.library.path=/home/godhuli/custom/hadoop/bin/../lib/native/Linux-amd64-64:/home/godhuli/custom/hdfs/mapred/local/taskTracker/jobcache/job_200812282102_0003/attempt_200812282102_0003_m_000000_0/work
-Xmx200m -Djava.io.tmpdir=/home/godhuli/custom/hdfs/mapred/local/taskTracker/jobcache/job_200812282102_0003/attempt_200812282102_0003_m_000000_0/work/tmp
-classpath /attempt_200812282102_0003_m_000000_0/work
-Dhadoop.log.dir=/home/godhuli/custom/hadoop/bin/../logs
-Dhadoop.root.logger=INFO,TLA
-Dhadoop.tasklog.taskid=attempt_200812282102_0003_m_000000_0
-Dhadoop.tasklog.totalLogFileSize=0 org.apache.hadoop.mapred.Child
127.0.0.1 40443 attempt_200812282102_0003_m_000000_0 1525207782

Also, the reducer only used 540mb. I notice -Xmx200m was passed, how
to change it?
Regards
Saptarshi

On Sun, Dec 28, 2008 at 10:19 PM, Saptarshi Guha
<saptarshi.guha@gmail.com> wrote:
> On Sun, Dec 28, 2008 at 4:33 PM, Brian Bockelman <bbockelm@cse.unl.edu> wrote:
>> Hey Saptarshi,
>>
>> Watch the running child process while using "ps", "top", or Ganglia
>> monitoring.  Does the map task actually use 16GB of memory, or is the memory
>> not getting set properly?
>>
>> Brian
>
> I haven't figured out how to run ganglia, however, also the children
> quit before i can see their memory usage. The trackers all use
> 16GB.(from the ps command). However, i noticed some use 512MB
> only(when i manged to catch them in time)
>
> Regards
>


-- 
Saptarshi Guha - saptarshi.guha@gmail.com