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 are implemented incorrectly
Date Wed, 08 Jun 2016 18:18:21 GMT

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

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

Julia, the above comment is not clear to me. Can you elaborate? However, if I try to extrapolate,
is this what you are trying to say:

UpdateTaskHost broadcasts STOP signal to all the mappers and then notifies the driver that
it is done and wait for driver to send a close signal. After driver receives the signal from
master, it knows that IMRU has completed, signals the master to stop and ignore any task failures
from mappers. 

However, it can receive map task failures before it receives done signal from the master.
So this makes the logic complicated right? If  not, and you have a workaround, I am in for
the solution.

> 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