You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Stephan Ewen (JIRA)" <ji...@apache.org> on 2016/02/08 17:04:39 UTC
[jira] [Commented] (FLINK-3369) RemoteTransportException should be
instance of CancelTaskException
[ https://issues.apache.org/jira/browse/FLINK-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15137137#comment-15137137 ]
Stephan Ewen commented on FLINK-3369:
-------------------------------------
In the long run, I think it makes sense that this exception is reported to the JobManager.
We can use this to learn that the source task manager has a problem, and not deploy further tasks to it unless it has pinged back, for example.
> RemoteTransportException should be instance of CancelTaskException
> ------------------------------------------------------------------
>
> Key: FLINK-3369
> URL: https://issues.apache.org/jira/browse/FLINK-3369
> Project: Flink
> Issue Type: Bug
> Reporter: Ufuk Celebi
> Assignee: Ufuk Celebi
> Fix For: 1.0.0
>
>
> {{RemoteTransportException}} is thrown when a consuming task is notified about failure at the producer side. This should not be reported as the root cause of the job failure. By making it an instance of {{CancelTaskException}} it will not be reported as a failure, but as a cancellation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)