[
https://issues.apache.org/jira/browse/FLINK-6043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938840#comment-15938840
]
ASF GitHub Bot commented on FLINK-6043:
---------------------------------------
Github user tillrohrmann commented on a diff in the pull request:
https://github.com/apache/flink/pull/3583#discussion_r107731433
--- Diff:
flink-runtime/src/main/java/org/apache/flink/runtime/executiongraph/ExecutionGraph.java
---
@@ -210,7 +210,7 @@
/** The exception that caused the job to fail. This is set to the first
root exception
* that was not recoverable and triggered job failure */
- private volatile Throwable failureCause;
+ private final ErrorInfo failureCause = new ErrorInfo();
--- End diff --
making the fields of the `ErrorInfo` final and `failureCause` volatile is
better imho.
> Display time when exceptions/root cause of failure happened
> -----------------------------------------------------------
>
> Key: FLINK-6043
> URL: https://issues.apache.org/jira/browse/FLINK-6043
> Project: Flink
> Issue Type: Improvement
> Components: Webfrontend
> Affects Versions: 1.3.0
> Reporter: Till Rohrmann
> Assignee: Chesnay Schepler
> Priority: Minor
>
> In order to better understand the behaviour of Flink jobs, it would be nice
> to add timestamp information to exception causing the job to restart or to
> fail. This information could then be displayed in the web UI making it easier
> for the user to understand what happened when.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
