You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2017/03/30 15:55:42 UTC
[jira] [Closed] (FLINK-5302) Log failure cause at Execution
[ https://issues.apache.org/jira/browse/FLINK-5302?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Chesnay Schepler closed FLINK-5302.
-----------------------------------
Resolution: Invalid
We already store the failureCause for each execution.
> Log failure cause at Execution
> -------------------------------
>
> Key: FLINK-5302
> URL: https://issues.apache.org/jira/browse/FLINK-5302
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination
> Reporter: Ufuk Celebi
>
> 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.15#6346)