hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon" <edwardy...@apache.org>
Subject Re: setNumBspTask
Date Sun, 17 Apr 2011 22:14:04 GMT
> I think we should document that this is a mandatory call to a job OR set
> this in submitJobInternal of the BSPJobClient to the number of active
> grooms.
> What's your opinion on that?

+1

And,
It is highly related with HAMA-199. Our 'sync barrier' is very naive.
We should fix this problem as soon as possible.

On Mon, Apr 18, 2011 at 3:20 AM, Thomas Jungblut
<thomas.jungblut@googlemail.com> wrote:
> Hi all,
>
> I played a bit with submitting BSP's from other applications and seen that
> setting the num of BSP tasks is a mandatory action.
> Otherwise the job will hang forever with this output:
>
> 11/04/17 20:07:50 INFO bsp.BSPJobClient: Running job: job_201104172007_0001
>> 11/04/17 20:07:53 INFO bsp.BSPJobClient: Current supersteps number: 0
>>
>
> I think we should document that this is a mandatory call to a job OR set
> this in submitJobInternal of the BSPJobClient to the number of active
> grooms.
> What's your opinion on that?
>
> Regards
> Thomas
>
> --
> Thomas Jungblut
> Berlin
>
> mobile: 0170-3081070
>
> business: thomas.jungblut@testberichte.de
> private: thomas.jungblut@gmail.com
>



-- 
Best Regards, Edward J. Yoon
http://blog.udanax.org
http://twitter.com/eddieyoon

Mime
View raw message