Mailing-List: contact giraph-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: giraph-user@incubator.apache.org
Message-ID: <4F9FF6F2.7000208@apache.org>
Date: Tue, 01 May 2012 07:45:06 -0700
From: Avery Ching <aching@apache.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: giraph-user@incubator.apache.org
Subject: Re: Giraph still running after mappers are 100% finished ?
References: <FF7D7B51-A21F-4C8C-BA20-32F890873469@deri.org>
In-Reply-To: <FF7D7B51-A21F-4C8C-BA20-32F890873469@deri.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Benjamin,

I wonder if the issues you are seeing are related to 
https://issues.apache.org/jira/browse/GIRAPH-169.

This shouldn't happen.

Avery

On 5/1/12 7:29 AM, Benjamin Heitmann wrote:
> Hello,
>
> under which circumstances is it possible that a Giraph job, will report that he is 100% finished will his mappers,
> but the job is still running ?
>
> I can see that it is still running from:
> * debugging messages,
> * list of running threads (in top)
> * the hadoop jobtracker web site (it reports 100% completion of mappers, but also that all mappers are running, and none is complete)
>
> I am currently running some benchmarks to get a handle on the scalability of giraph and of my algorithm implementation.
> And the results up to now are very confusing...
>
>
> Looking forward to any answers, cheers, Benjamin.