-histo:live namenodepid*
> --
> *From:* Personal [nitin.mo...@gmail.com]
> *Sent:* Tuesday, June 18, 2013 7:20 AM
> *To:* user@hadoop.apache.org
> *Subject:* Re: Namenode memory usage
>
>
> E Lego
>
>
> On Mon, Jun 17, 2013 at 1:04 PM, Patai Sangbutsarakum <
&g
Can you take heapdump and check ..? Here you can check which objects are using
how much..
Command : jmap -histo:live namenodepid
From: Personal [nitin.mo...@gmail.com]
Sent: Tuesday, June 18, 2013 7:20 AM
To: user@hadoop.apache.org
Subject: Re: Namenode memory
E Lego
On Mon, Jun 17, 2013 at 1:04 PM, Patai Sangbutsarakum
wrote:
> Hi Hadoopers,
> My dedicated Namenode box has 48G of memory, 40G is allocated for NN. HEAP
> This is from 50070/dfshealth.jsp
> *28540193 files and directories, 32324098 blocks = 60864291 total. Heap
> Size is 23.34 GB / 38.54
Chris, Thanks a million; it's the huge relieve.
My next action is turn on the GC and verify if it ever goes to full GC a
lot.
I do appreciate your help.
On Mon, Jun 17, 2013 at 2:56 PM, Chris Nauroth wrote:
> Hello Patai,
>
> The numbers you see there (23.34 GB / 38.54 GB) are the JVM total mem
Hello Patai,
The numbers you see there (23.34 GB / 38.54 GB) are the JVM total memory /
max memory.
The max memory is always going to be equivalent to your -Xmx setting
(4m). This is the maximum amount of memory that the JVM will attempt
to allocate from the OS.
The total memory is the amou
Hi Hadoopers,
My dedicated Namenode box has 48G of memory, 40G is allocated for NN. HEAP
This is from 50070/dfshealth.jsp
*28540193 files and directories, 32324098 blocks = 60864291 total. Heap
Size is 23.34 GB / 38.54 GB (60%) *
*The Heap is fluctuating between less than 20G up to almost 100%*
