Return-Path: Delivered-To: apmail-incubator-hama-dev-archive@minotaur.apache.org Received: (qmail 39807 invoked from network); 18 Apr 2011 09:19:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 18 Apr 2011 09:19:56 -0000 Received: (qmail 71017 invoked by uid 500); 18 Apr 2011 09:19:56 -0000 Delivered-To: apmail-incubator-hama-dev-archive@incubator.apache.org Received: (qmail 69098 invoked by uid 500); 18 Apr 2011 09:19:50 -0000 Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hama-dev@incubator.apache.org Delivered-To: mailing list hama-dev@incubator.apache.org Received: (qmail 69083 invoked by uid 99); 18 Apr 2011 09:19:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Apr 2011 09:19:43 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=MIME_QP_LONG_LINE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.83.175] (HELO mail-pv0-f175.google.com) (74.125.83.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Apr 2011 09:19:37 +0000 Received: by pvc30 with SMTP id 30so2200939pvc.6 for ; Mon, 18 Apr 2011 02:19:17 -0700 (PDT) Received: by 10.68.23.41 with SMTP id j9mr6291916pbf.51.1303118357154; Mon, 18 Apr 2011 02:19:17 -0700 (PDT) Received: from [1.107.233.109] ([1.107.233.109]) by mx.google.com with ESMTPS id d9sm2189316pba.16.2011.04.18.02.19.14 (version=TLSv1/SSLv3 cipher=OTHER); Mon, 18 Apr 2011 02:19:16 -0700 (PDT) Subject: Re: setNumBspTask References: From: "Edward J. Yoon" Content-Type: text/plain; charset=euc-kr X-Mailer: iPhone Mail (8H7) In-Reply-To: Message-Id: Date: Mon, 18 Apr 2011 18:19:04 +0900 To: "hama-dev@incubator.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (iPhone Mail 8H7) > groom can leave the sync process and the other grooms will advance without= waiting for the finished groom. It's impossible. Sent from my iPhone On 2011. 4. 18., at =BF=C0=C8=C4 6:08, Thomas Jungblut wrote: > Should I open a new issue for it? >=20 > 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. >=20 > 2011/4/18 Edward J. Yoon >=20 >>> 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? >>=20 >> +1 >>=20 >> And, >> It is highly related with HAMA-199. Our 'sync barrier' is very naive. >> We should fix this problem as soon as possible. >>=20 >> On Mon, Apr 18, 2011 at 3:20 AM, Thomas Jungblut >> wrote: >>> Hi all, >>>=20 >>> 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: >>>=20 >>> 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 >>>>=20 >>>=20 >>> 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? >>>=20 >>> Regards >>> Thomas >>>=20 >>> -- >>> Thomas Jungblut >>> Berlin >>>=20 >>> mobile: 0170-3081070 >>>=20 >>> business: thomas.jungblut@testberichte.de >>> private: thomas.jungblut@gmail.com >>>=20 >>=20 >>=20 >>=20 >> -- >> Best Regards, Edward J. Yoon >> http://blog.udanax.org >> http://twitter.com/eddieyoon >>=20 >=20 >=20 >=20 > --=20 > Thomas Jungblut > Berlin >=20 > mobile: 0170-3081070 >=20 > business: thomas.jungblut@testberichte.de > private: thomas.jungblut@gmail.com