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 in failure case
Date Tue, 31 May 2016 20:05:12 GMT

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

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

And BTW this applies to one chunk also...What is all this happens when a part of chunk has
been read and so on. The other side might resend the packages but then some sort of version
control is needed where we need to make sure that the previous messages are not being received.

Bottomline, I am trying to convey that this logic of Task re-doing the broadcast and reduce
operation is not straightforward. Any such logic has to be intrinsicallt part of GC.

> Catching exceptions in group communication in failure case
> ----------------------------------------------------------
>
>                 Key: REEF-1407
>                 URL: https://issues.apache.org/jira/browse/REEF-1407
>             Project: REEF
>          Issue Type: Bug
>            Reporter: Julia
>              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