You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Markus Weimer (JIRA)" <ji...@apache.org> on 2015/07/09 22:56:05 UTC

[jira] [Resolved] (REEF-453) Race condition in GroupCommunication Client initialization

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

Markus Weimer resolved REEF-453.
--------------------------------
    Resolution: Fixed

Fixed via [#278|https://github.com/apache/incubator-reef/pull/278]

> Race condition in GroupCommunication Client initialization
> ----------------------------------------------------------
>
>                 Key: REEF-453
>                 URL: https://issues.apache.org/jira/browse/REEF-453
>             Project: REEF
>          Issue Type: Bug
>            Reporter: Julia
>            Assignee: Julia
>             Fix For: 0.12
>
>
> In GroupCommClient constructor, we register the task node to Name Server first, then instantiate CommunicationGroupClient, which will instantiate Operators and register handlers. In Operator constructors, we check if its parents and children are all registered based on the topology. There is a chance that a parent or a child was registered, but haven't completed the initialization, resulting a race condition. 
> We need to make sure for each task, all the initializations must be completed then does registration. 



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