/2014 05:36 PM
Subject:Re: Java Process Memory Leak
Interesting find.. It looks that bit was added recently (
https://reviews.apache.org/r/17644/diff/3/) and so was not part of Giraph
1.0.0 as far as I can tell.
Also, if anyone cares, a clunky (Ubuntu) workaround I'm using is: kill
$(ps
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
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
Oh, I see. I did jstack on a cluster of machines and a single machine...
I'm not quite sure how to interpret the output. My best guess is that there
might be a deadlock---there's just a bunch of Netty threads waiting. The
links to the jstack dumps:
http://pastebin.com/0cLuaF07 (PageRank,
termination call seems to be waiting on the
executionGroup instead of the workerGroup...
Craig M.
From: Young Han young@uwaterloo.ca
To: user@giraph.apache.org
Date: 03/17/2014 03:25 PM
Subject:Re: Java Process Memory Leak
Oh, I see. I did jstack on a cluster of machines
@giraph.apache.org
Date:03/17/2014 03:25 PM
Subject:Re: Java Process Memory Leak
--
Oh, I see. I did jstack on a cluster of machines and a single machine...
I'm not quite sure how to interpret the output. My best guess is that there
might be a deadlock
