Mailing-List: contact user-help@giraph.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@giraph.apache.org
Message-ID: <5327208B.4060905@apache.org>
Date: Mon, 17 Mar 2014 09:19:23 -0700
From: Avery Ching <aching@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9;
 rv:24.0) Gecko/20100101 Thunderbird/24.3.0
MIME-Version: 1.0
To: user@giraph.apache.org
Subject: Re: Java Process Memory Leak
References: 
 <CAHKqz0fn+taCodt+oP0EBcugi2PwLBOD+yyrHuBPBEhEB6OLJw@mail.gmail.com>
In-Reply-To: 
 <CAHKqz0fn+taCodt+oP0EBcugi2PwLBOD+yyrHuBPBEhEB6OLJw@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi Young,

Our Hadoop instance (Corona) kills processes after they finish executing 
so we don't see this.  You might want to do a jstack to see where it's 
hung up on and figure out the issue.

Thanks

Avery

On 3/17/14, 7:56 AM, Young Han wrote:
> Hi all,
>
> With Giraph 1.0.0, I've noticed an issue where the Java process 
> corresponding to the job loiters around indefinitely even after the 
> job completes (successfully). The process consumes memory but not CPU 
> time. This happens on both a single machine and clusters of machines 
> (in which case every worker has the issue). The only way I know of 
> fixing this is killing the Java process manually---restarting or 
> stopping Hadoop does not help.
>
> Is this some known bug or a configuration issue on my end?
>
> Thanks,
> Young