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

Posted to dev@giraph.apache.org by "Maja Kabiljo (JIRA)" <ji...@apache.org> on 2012/10/16 02:25:03 UTC

[jira] [Commented] (GIRAPH-372) Write worker addresses to Zookeeper; move addresses and resolution to NettyClient

    [ https://issues.apache.org/jira/browse/GIRAPH-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13476601#comment-13476601 ] 

Maja Kabiljo commented on GIRAPH-372:
-------------------------------------

https://reviews.apache.org/r/7610/
                
> Write worker addresses to Zookeeper; move addresses and resolution to NettyClient
> ---------------------------------------------------------------------------------
>
>                 Key: GIRAPH-372
>                 URL: https://issues.apache.org/jira/browse/GIRAPH-372
>             Project: Giraph
>          Issue Type: Improvement
>            Reporter: Maja Kabiljo
>            Assignee: Maja Kabiljo
>         Attachments: GIRAPH-372.patch
>
>
> In preparation for GIRAPH-273, we need to have addresses of all workers available, so I write them to Zookeeper along with the master address.
> Since address resoultion is needed in both NettyWorkerClient and NettyMasterClient, I moved that to NettyClient, and also added a map taskId->address in there. Now NettyMasterClient and NettyWorkerClient don't need to take care of InetSocketAddresses, just task ids which they want to send messages to.

--
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