incubator-hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Jungblut (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HAMA-387) Advanced Barrier Synchronization
Date Fri, 23 Sep 2011 18:40:26 GMT

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

Thomas Jungblut updated HAMA-387:
---------------------------------

    Attachment: ownSyncService_v2.patch

fixed checkpointer testcase

> 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: ChiaHung Lin
>             Fix For: 0.4.0
>
>         Attachments: HAMA-387.patch, HAMA-387_v02.patch, HAMA-387_v03.patch, HAMA-387_v04.patch,
doublebarrier.patch, new.patch, ownSyncService.patch, ownSyncService_v2.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

        

Mime
View raw message