Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of
 thomas.jungblut@googlemail.com designates 209.85.212.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type;
        b=yFt+Dxac54ukOfevS34MZjKdnlmXcecZZtGkRTeR4gHG/3fS5aAar7gJ9HZubmTYBB
         MMHSGk3uufN+Ll7k/2kZl108Yja+uXhAyyU1OVvRrWdTK6/JXx5uALyu9ceopWlz3uDq
         3VPnLFyp3W19b/Dt97c/fUu8EPgw2xZFkPVp0=
MIME-Version: 1.0
In-Reply-To: <BANLkTikH8a7KhAFe_UoziqneSLgbWCZtpw@mail.gmail.com>
References: <BANLkTikakAwTPGJv14u9gm0QYAKyUcB8bw@mail.gmail.com>
	<BANLkTikH8a7KhAFe_UoziqneSLgbWCZtpw@mail.gmail.com>
Date: Mon, 18 Apr 2011 11:08:53 +0200
Message-ID: <BANLkTiktgTUhBQKft6OEsj7d5=NbZWbp8g@mail.gmail.com>
Subject: Re: setNumBspTask
From: Thomas Jungblut <thomas.jungblut@googlemail.com>
To: hama-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=20cf30549fe3999cb504a12dbdce

--20cf30549fe3999cb504a12dbdce
Content-Type: text/plain; charset=ISO-8859-1

Should I open a new issue for it?

Agree with the sync barrier.
In addition to that, we should add an equal version of voteForHalt() where a
groom can leave the sync process and the other grooms will advance without
waiting for the finished groom.

2011/4/18 Edward J. Yoon <edwardyoon@apache.org>

> > 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
>


-- 
Thomas Jungblut
Berlin

mobile: 0170-3081070

business: thomas.jungblut@testberichte.de
private: thomas.jungblut@gmail.com

--20cf30549fe3999cb504a12dbdce--