Mailing-List: contact hama-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hama-dev@incubator.apache.org
Date: Wed, 14 Sep 2011 12:15:09 +0000 (UTC)
From: "ChiaHung Lin (JIRA)" <jira@apache.org>
To: hama-dev@incubator.apache.org
Message-ID: 
 <1560487672.26374.1316002509482.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1217210581.8823.1305248867332.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (HAMA-387) Advanced Barrier Synchronization
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/HAMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ChiaHung Lin updated HAMA-387:
------------------------------

    Attachment: x.patch

Any chance to help test the patch and paste the log so I can check its internal state? Basically just to know when sync() hangs, within super step what process remains there. I've tested this patch with 5 vms and it works ok, but I understand this is probably because the processes involved are not large enough. 

> Advanced Barrier Synchronization
> --------------------------------
>
>                 Key: HAMA-387
>                 URL: https://issues.apache.org/jira/browse/HAMA-387
>             Project: Hama
>          Issue Type: Improvement
>          Components: bsp
>    Affects Versions: 0.3.0
>            Reporter: Edward J. Yoon
>            Assignee: Edward J. Yoon
>             Fix For: 0.4.0
>
>         Attachments: HAMA-387_v02.patch, HAMA-387_v03.patch, HAMA-387_v04.patch, new.patch, sleepless.patch, x.PNG, x.patch
>
>
> I think, the lock file must include:
>  * the job ID
>  * the task ID of the lock file owner
>  * the current superstep count
> to check ownership and validation.
> Currently they are named by hostname, but multi-tasks can be run per one groomserver in the future. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira