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 are implemented incorrectly
Date Tue, 07 Jun 2016 18:52:20 GMT


Dhruv Mahajan commented on REEF-1407:

So in group comm., if 0 would like to broadcast, with tree topology, it first writes to 1
and then writes to 2. So, on writing to 1 first it gets an error message and hence will never
write to 2. We have two options: an error is thrown but is suppressed somewhere in 0 without
closing all the connection related to group comm. in 0. In this case 2 will forever be waiting
on data from 0. The second option is to make sure that anytime error happens in 0, the whole
group communication will be closed or disposed (automatically or explicitly). This way 2 will
also be bale to receive broken connection error and close down.

> Catching exceptions in group communication are implemented incorrectly
> ----------------------------------------------------------------------
>                 Key: REEF-1407
>                 URL:
>             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

View raw message