You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@flink.apache.org by "Ufuk Celebi (JIRA)" <ji...@apache.org> on 2016/12/08 23:08:58 UTC

[jira] [Created] (FLINK-5302) Log failure cause at Execution

Ufuk Celebi created FLINK-5302:
----------------------------------

             Summary: Log failure cause at Execution 
                 Key: FLINK-5302
                 URL: https://issues.apache.org/jira/browse/FLINK-5302
             Project: Flink
          Issue Type: Improvement
            Reporter: Ufuk Celebi
             Fix For: 1.2.0, 1.1.4


It can be helpful to log the failure cause that made an {{Execution}} switch to state {{FAILED}}. We currently only see a "root cause" logged on the JobManager, which happens to be the first failure cause that makes it to {{ExecutionGraph#fail()}}. This depends on relative timings of messages. For debugging it can be helpful to have all causes available.



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