You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@hama.apache.org by "Suraj Menon (JIRA)" <ji...@apache.org> on 2012/10/08 14:08:03 UTC

[jira] [Updated] (HAMA-652) Synchronization mechanism should let peers to sync on different synchronization point and close the ZK connection when done.

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

Suraj Menon updated HAMA-652:
-----------------------------

    Attachment: HAMA-652.patch-v1

Attaching the current version. The patch is not completely tested. TestBSPMasterGroomServer is failing. Investigating on that and adding a unit test specific for barrier implementation in TestZookeeper. 

The idea here is instead of comparing with the total number of peers in the system, it compares with the peers already registered for that synchronization. The synchronization membership for each sync point as well as all the sync points could be defined as early as during the job initialization and as late as the previous sync of all the peers. While closing, the peers remove their membership in all the sync points they had previously registered for.
                
> Synchronization mechanism should let peers to sync on different synchronization point and close the ZK connection when done.
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HAMA-652
>                 URL: https://issues.apache.org/jira/browse/HAMA-652
>             Project: Hama
>          Issue Type: New Feature
>          Components: bsp core
>            Reporter: Suraj Menon
>            Assignee: Suraj Menon
>         Attachments: HAMA-652.patch-v1
>
>
> This feature should allow the synchronization API to let 
> - Peers to enter synchronization selectively with each other.
> - Peers should be able to close self on completion and other running peers should be able to sync and continue.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira