reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Julia (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1407) Catching exceptions in group communication are implemented incorrectly
Date Wed, 21 Sep 2016 17:47:20 GMT

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

Julia commented on REEF-1407:
-----------------------------

The issue was/is the network exception from a separate thread (cannot read bytes e.g. thrown
from StreamingTransportClient and StreamingTransportServer) should be caught and propagated
to the observer through Oberver.OnError() and properly caught at task. Now they are still
floating in the air. 

Andrew has changed the GC observer structure to make this fix possible. 

> 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