reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dhruv Mahajan (JIRA)" <>
Subject [jira] [Commented] (REEF-1407) Catching exceptions in group communication in failure case
Date Wed, 01 Jun 2016 17:32:59 GMT


Dhruv Mahajan commented on REEF-1407:

[~markus.weimer] yes that's what I am saying. [~juliaw] it's the same thing. {{OnNext}}, {{OnCompleted}}
and {{OnError}} are part of same interface and any of them can be used. When I say end message/flag,
its sort of a special kind of message for each IObserver container. They will receive this
message, package it further and call {{OnError}} or {{OnCompleted}} of upstream observers.
The end observer is the Blocking collection on which GC operators might be waiting. There
are three cases: a) They are actively waiting on Blocking collection, GC will now come out
and throw error/exception, b) GC will enter it at some point of time, the behaviour will be
same as a) since message will be in the collection, c) GC never reads it since it is done
with operators and all, and message came since underlying streams were closed. In this case
they will be ignored since no operator will be called again.

> Catching exceptions in group communication in failure case
> ----------------------------------------------------------
>                 Key: REEF-1407
>                 URL:
>             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

View raw message