reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (REEF-1320) Creating default communication group in passive way
Date Tue, 12 Apr 2016 21:06:25 GMT

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

Markus Weimer resolved REEF-1320.
---------------------------------
       Resolution: Done
    Fix Version/s: 0.15

Done via [#930|https://github.com/apache/reef/pull/930]

> Creating default communication group in passive way
> ---------------------------------------------------
>
>                 Key: REEF-1320
>                 URL: https://issues.apache.org/jira/browse/REEF-1320
>             Project: REEF
>          Issue Type: Task
>          Components: IMRU, REEF.NET
>            Reporter: Julia
>            Assignee: Julia
>              Labels: FT
>             Fix For: 0.15
>
>
> In Fault Tolerant scenarios, we will generate a new group during the recovery. And the
same code should be shared no matter it is for the first group or a new group.
> In IMRU driver, there is only one GroupCommDriver instance. Current default group is
created in the constructor of GroupCommDriver. That would enforce us to get the first group
in different way from rest of the groups. And if we want to share the same code for all the
group creations right before submitting the tasks, we have to remove the default one. That
is not a right approach.
> We should move the default group creation from the constructor of communication group
driver. It would be created only when it is called. 
> In fault tolerant case, we will not use the default group but call NewCommunicationGroup()
before tasks are submitted. 



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

Mime
View raw message