You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Mariia Mykhailova (JIRA)" <ji...@apache.org> on 2016/09/14 03:07:20 UTC

[jira] [Resolved] (REEF-1549) Resolve the issue in WaitingForRegistration

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

Mariia Mykhailova resolved REEF-1549.
-------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.16

Resolved via [PR 1117|https://github.com/apache/reef/pull/1117]

> Resolve the issue in WaitingForRegistration
> -------------------------------------------
>
>                 Key: REEF-1549
>                 URL: https://issues.apache.org/jira/browse/REEF-1549
>             Project: REEF
>          Issue Type: Improvement
>    Affects Versions: 0.16
>            Reporter: Julia
>            Assignee: Julia
>              Labels: FT
>             Fix For: 0.16
>
>
> Currently, if an elevator fails while we are still in the phase of task submission, we will have an issue where the newly created tasks will wait in WaitForRegistration in Group communication initialization until timeout. 
> A way to do it is to cancel the task that is in constructing. The issue is the driver has not received IRunningTask yet at this time therefore there is no way to send event to the task with the current system.
> Another way is to add a context layer for group communication initialization. Let Driver/GroupCommuDriver to control if all such contexts are created based on the context event. Then  submitting tasks on those contexts. This would keep the control for group communications in a centralized place. It would also makes task initialization much quicker and reduce the chance to get failures in task constructor before task is running. 



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