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

Posted to dev@hama.apache.org by "Edward J. Yoon (JIRA)" <ji...@apache.org> on 2015/02/12 06:44:12 UTC

[jira] [Updated] (HAMA-728) BSP Messaging API and user APIs should refer to peers with reference to their global peer task id.

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

Edward J. Yoon updated HAMA-728:
--------------------------------
    Fix Version/s:     (was: 0.7.0)

> BSP Messaging API and user APIs should refer to peers with reference to their global peer task id.
> --------------------------------------------------------------------------------------------------
>
>                 Key: HAMA-728
>                 URL: https://issues.apache.org/jira/browse/HAMA-728
>             Project: Hama
>          Issue Type: New Feature
>            Reporter: Suraj Menon
>
> Today we are referring to the peers as hostname:port. This is not a good idea, considering on fault recovery the peer address changes. We can make the ZK synchronization service to keep a map/array of peer ID's to the peer connection details. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)