reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhruv Mahajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1407) Catching exceptions in group communication are implemented incorrectly
Date Sun, 12 Jun 2016 18:15:21 GMT

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

Dhruv Mahajan commented on REEF-1407:
-------------------------------------

[~markus.weimer] [~juliaw], [~afchung90] and I have been looking at this together for 3-4
days trying to come up with some fix and solution. At the end of it we both have concluded
that current Wake.Remote design is not sufficient to address the issue of this JIRA. Problem
is that on Server side we register a Universal observer that listens to messages from all
the remote endpoints. Hence, if one end point finishes and we want to propagate completion
upstream to group communication it is not currently possible to do so. Hence, we need to change
these layers so that instead of registering a UniversalObserver we sort of have an observer
per connection.

[~afchung90] will file in JIRA for this soon.

> Catching exceptions in group communication are implemented incorrectly
> ----------------------------------------------------------------------
>
>                 Key: REEF-1407
>                 URL: https://issues.apache.org/jira/browse/REEF-1407
>             Project: REEF
>          Issue Type: Bug
>            Reporter: Julia
>            Assignee: Dhruv Mahajan
>              Labels: FT
>
> Currently when a task fails, other tasks in the group are stuck in reading data by a
blocking call. We should be able to try and throw an exception and propagate the exception
to Task so that the task can handle it in a proper way. 



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

Mime
View raw message