incubator-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: [jira] [Commented] (HAMA-387) Add task ID and superstep count informations to lock file
Date Fri, 15 Jul 2011 09:16:31 GMT
Haha yes.

+1

Sent from my iPhone

On 2011. 7. 15., at 오후 6:10, "Thomas Jungblut (JIRA)" <jira@apache.org> wrote:

> 
>    [ https://issues.apache.org/jira/browse/HAMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13065791#comment-13065791
] 
> 
> Thomas Jungblut commented on HAMA-387:
> --------------------------------------
> 
> You just took the code from zookeepers barrier sync example right?:D
> 
> I would prefer a self-written solution as stated in the first post..
> 
>> Add task ID and superstep count informations to lock file
>> ---------------------------------------------------------
>> 
>>                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
>> 
>> 
>> 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
> 
> 

Mime
View raw message