reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Chung (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1407) Catching exceptions in group communication are implemented incorrectly
Date Mon, 13 Jun 2016 16:55:21 GMT

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

Andrew Chung commented on REEF-1407:
------------------------------------

The main problem is that in {{StreamingNetworkService}}, we are only registering one {{IObserver<NsMessage>}}
for the {{Server}}, i.e. the universal observer. This means that all the demultiplexing has
to happen at the level above {{StreamingNetworkService}}. Thus, as of today wee are not able
to use {{OnError}} without wrapping a new, specific type of {{Exception}}, nor are we able
to use {{OnComplete}} directly since we are not able to know which sender from the remote
end closed the connection.

> 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