flink-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ufuk Celebi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FLINK-3369) RemoteTransportException should be instance of CancelTaskException
Date Thu, 11 Feb 2016 10:52:18 GMT

    [ https://issues.apache.org/jira/browse/FLINK-3369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15142569#comment-15142569

Ufuk Celebi commented on FLINK-3369:

Yes, for example if the connection is lost, I agree that it makes sense to take this into
account. But currently with what we have, this is mostly confusing to users.

> 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

View raw message