Return-Path: Delivered-To: apmail-incubator-hama-dev-archive@minotaur.apache.org Received: (qmail 29596 invoked from network); 25 Jan 2011 19:57:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 25 Jan 2011 19:57:05 -0000 Received: (qmail 33844 invoked by uid 500); 25 Jan 2011 19:57:05 -0000 Delivered-To: apmail-incubator-hama-dev-archive@incubator.apache.org Received: (qmail 33773 invoked by uid 500); 25 Jan 2011 19:57:04 -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 33765 invoked by uid 99); 25 Jan 2011 19:57:04 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jan 2011 19:57:04 +0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of clin4j@googlemail.com designates 209.85.216.47 as permitted sender) Received: from [209.85.216.47] (HELO mail-qw0-f47.google.com) (209.85.216.47) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 25 Jan 2011 19:56:58 +0000 Received: by qwi2 with SMTP id 2so164969qwi.6 for ; Tue, 25 Jan 2011 11:56:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type:content-transfer-encoding; bh=FnpuKQ0hsmo4mpV1IgoTX3F7ulv2JtYnNmw1x2Oe+sM=; b=Nkb1ByiqaBeouHO+Y+wiNaaB5ZHZmTD2KDF3zhOACM4uSMrkGpnI13Zg6ZL6p3JteO WLpre/hMW+o+v5MQMQLpI2yMxW41IzWUxwFMjHXhRz9wDC2WOKP9jSDZ+nD1QbEqz6Tb n9MvINxMAM0gXPe5CMnuvFcbDJ5I5P5Fa2irQ= 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:content-transfer-encoding; b=nyt+yAwk/6FcgLauHcz3/tbzTPxxAGd+G2/q6MPHGe0Kn7+EdswsYLjLe+foDj8Kfs yAwq7p9gfv7P5SnWVKVdMpjBnXjUvYTCLECYCklx0KKlHuLwb1gXD6hP+dq5C40TsqhJ YXjwRi8vZiT+qcNMK5zDE1NSuvk6/r9ZSMES4= MIME-Version: 1.0 Received: by 10.229.215.9 with SMTP id hc9mr5050654qcb.117.1295985395782; Tue, 25 Jan 2011 11:56:35 -0800 (PST) Received: by 10.229.1.147 with HTTP; Tue, 25 Jan 2011 11:56:35 -0800 (PST) In-Reply-To: References: <92C1387F-F4BC-4C75-B86A-E307E4774ED6@udanax.org> Date: Wed, 26 Jan 2011 03:56:35 +0800 Message-ID: Subject: Re: Fail to communicate with BSPMaster for reporting. From: Chia-Hung Lin To: hama-dev@incubator.apache.org Content-Type: text/plain; charset=EUC-KR Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org I add a few lines regarding to the coding style currently I discover so far, but other convention may require more discussion if needed. Please correct me and help me add new one for that section as appropriate. Thanks. 2011/1/24 Edward J. Yoon : > Yup, pls feel free to open new wiki page on http://wiki.apache.org/hama > > Let's clarify our coding standards. > > 2011/1/24 Chia-Hung Lin : >> Is there any chance that this information can be described in HAMA >> developer page? I went through the website and checked Apache >> Contributor Documentation, but seems there is no mention about such >> convention (maybe I miss it somewhere else). So I make use of coding >> style referred to at >> http://www.kernel.org/doc/Documentation/CodingStyle for local >> variables. >> >> I will prevent this next time. >> >> Thanks for the advice. >> >> 2011/1/21 Edward J. Yoon : >>> Great! >>> >>> And here's my one comment for you about instance/reference variables >>> naming. I think, they should say at least something about the object. >>> For example, >>> >>>>> GroomServerStatus gss; >>> >>> The "groomServerStatus" is much better and more readable than "gss" in >>> my opinion. :) >>> >>> 2011/1/21 Chia-Hung Lin : >>>> I've updated HAMA 346 with a patch that should fix the null value >>>> returned by whichJob(). >>>> >>>> 2011/1/21 Edward J. Yoon : >>>>> Thanks! >>>>> >>>>> =B3=AA=C0=C7 iPhone=BF=A1=BC=AD =BA=B8=B3=BF >>>>> >>>>> 2011. 1. 20. =BF=C0=C8=C4 11:06 Chia-Hung Lin = =C0=DB=BC=BA: >>>>> >>>>>> I check out source from svn with the revision r1058109 and this iss= ue >>>>>> also happens on my testing machines. >>>>>> >>>>>> It looks like the completion of task status is not consistent betwee= n >>>>>> GroomServers and BSPMaster. For insatnce, GroomServers report Tasks >>>>>> but JobInProgress consider tasks already been completed. But the >>>>>> detail may require more examine I will fix this as soon as possible. >>>>>> >>>>>> 2011/1/19 Edward J. Yoon : >>>>>>> Today, I noticed that there was a bug in the patch of HAMA-346. >>>>>>> >>>>>>> After first job execution completed, the BSPMaster.whichJob() retur= ns >>>>>>> null. So the BSP system always throws error message "Fail to >>>>>>> communicate with BSPMaster for reporting.". >>>>>>> >>>>>>> Simply, I'll add this code : "if (jip !=3D null) { }". >>>>>>> >>>>>>> What do you think? >>>>>>> >>>>>>> -- >>>>>>> Best Regards, Edward J. Yoon >>>>>>> http://blog.udanax.org >>>>>>> http://twitter.com/eddieyoon >>>>>>> >>>>> >>>> >>> >>> >>> >>> -- >>> Best Regards, Edward J. Yoon >>> http://blog.udanax.org >>> http://twitter.com/eddieyoon >>> >> > > > > -- > Best Regards, Edward J. Yoon > http://blog.udanax.org > http://twitter.com/eddieyoon >