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
