hama-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward J. Yoon (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HAMA-304) Allow BSP peers to get a list of all other peers executing tasks of the same job
Date Mon, 11 Oct 2010 06:42:32 GMT

    [ https://issues.apache.org/jira/browse/HAMA-304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12919734#action_12919734

Edward J. Yoon commented on HAMA-304:

And, it would be nice if we can get also the IDs of the bspPeer and task with hostname:port,
via getPeerAddresses() in BSP function. 

> Allow BSP peers to get a list of all other peers executing tasks of the same job
> --------------------------------------------------------------------------------
>                 Key: HAMA-304
>                 URL: https://issues.apache.org/jira/browse/HAMA-304
>             Project: Hama
>          Issue Type: New Feature
>            Reporter: Filipe Manana
>            Assignee: Filipe Manana
>         Attachments: hama-304.patch
> Hi,
> Currently (as in the PiEstimator example), when a peer wants to send a message to other
peer, it has to know in advance its hostname and port. This is likely fine for very small
clusters, but not convenient for reasonably sized clusters.
> The following patch allows a peer to get a list of all other peers (collection of InetSocketAddress)
so that it doesn't force a BSP job to know in advance the hostname and ports of the peers.
> The implementation might not be very efficient for very large clusters, as a list of
groom server addresses is sent in each HeartBeat response. This is something I think it should
be improved sometime later.
> Feedback welcome.
> cheers

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message