[jira] [Commented] (FLINK-7364) Log exceptions from user code in streaming jobs

["Stephan Ewen (JIRA)" <ji...@apache.org>]

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

Stephan Ewen commented on FLINK-7364:
-------------------------------------

Can you share some sample code where this happen?

So far, we were logging exceptions a lot (almost too much for some users), typically on the TaskManager, the JobManager's execution graph, and the Client.

I am a bit puzzled why your exception is not logged...

> Log exceptions from user code in streaming jobs
> -----------------------------------------------
>
>                 Key: FLINK-7364
>                 URL: https://issues.apache.org/jira/browse/FLINK-7364
>             Project: Flink
>          Issue Type: Bug
>          Components: Streaming
>    Affects Versions: 1.3.1
>            Reporter: Elias Levy
>
> Currently, if an exception arises in user supplied code within an operator in a streaming job, Flink terminates the job, but it fails to record the reason for the termination.  The logs do not record that there was an exception at all, much less recording the type of exception and where it occurred.  This makes it difficult to debug jobs without implementing exception recording code on all user supplied operators. 



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)