reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Markus Weimer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1447) Validate Task close failure => FailedEvaluator Event (task has not yet finished)
Date Wed, 22 Jun 2016 15:31:58 GMT

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

Markus Weimer commented on REEF-1447:
-------------------------------------

I see. But if the close handler and task itself are executed on different threads, this scheme
does not shut down the task anyway, right? The task would be stuck in the blocking call, and
we would not be able to reuse the Evaluator for another Task anyhow. Hence, I don't think
the current approach works irrespective of whether or not we implement this JIRA

The right solution seems to be to break out of the blocking call as you proposed in [REEF-1466].
Without that, we can't exit a Task that is stuck on the blocking read call.

> Validate Task close failure => FailedEvaluator Event (task has not yet finished)
> --------------------------------------------------------------------------------
>
>                 Key: REEF-1447
>                 URL: https://issues.apache.org/jira/browse/REEF-1447
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF.NET, REEF.NET Driver
>            Reporter: Andrew Chung
>            Assignee: Andrew Chung
>              Labels: FT
>
> We need to validate that an {{Exception}} in {{TaskCloseHandler}} triggers a {{FailedEvaluator}}
event on the Driver, if the Task has not yet completed.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message