[
https://issues.apache.org/jira/browse/HAMA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13114466#comment-13114466
]
Thomas Jungblut commented on HAMA-387:
--------------------------------------
{quote}
I don't see hang problem. Let's just put own barrier service on the back burner
for now.
{quote}
That's okay. If you have some time, I would be interested in a randbench result.
> 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, conditional_wait.patch, doublebarrier.patch, new.patch,
> ownSyncService.patch, ownSyncService_v2.patch, ownSyncService_v3.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
