[
https://issues.apache.org/jira/browse/FLINK-6042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15938218#comment-15938218
]
ASF GitHub Bot commented on FLINK-6042:
---------------------------------------
GitHub user zentol opened a pull request:
https://github.com/apache/flink/pull/3601
[WIP [FLINK-6042] [web] Display exception history
This is a work-in-progress PR building on top of #3583.
With this PR the exceptions tab in the web-interface now has 2 sub-tabs,
one for the most recent exception (the current Exception page) and another one
for a history of the last 20 root exceptions.
The history currently only displays root exceptions for the sake of
simplicity. The oldest exception is displayed at the bottom, so by scrolling
down you move back in time. Note that this tab only works for running jobs at
the moment, so if you want to try it out make sure you're setting a
restart-strategy.
The "Most recent" view (the current Exceptions page) was furthermore
enhanced to include the task name&location for the root exception. These are
only displayed when a task was responsible for a job failure.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zentol/flink 6042_excetion_history
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/3601.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #3601
----
commit d15f400a5f851e287d65e7da1af2e38a813dd74a
Author: zentol <ches...@apache.org>
Date: 2017-03-21T09:23:28Z
[FLINK-6043] [web] Display exception timestamp
commit bb879510bd65b54408b186a50f3e53b0c86b5236
Author: zentol <ches...@apache.org>
Date: 2017-03-23T11:51:11Z
[FLINK-6042] [web] Display exception history
----
> Display last n exceptions/causes for job restarts in Web UI
> -----------------------------------------------------------
>
> Key: FLINK-6042
> URL: https://issues.apache.org/jira/browse/FLINK-6042
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Coordination, Webfrontend
> Affects Versions: 1.3.0
> Reporter: Till Rohrmann
>
> Users requested that it would be nice to see the last {{n}} exceptions
> causing a job restart in the Web UI. This will help to more easily debug and
> operate a job.
> We could store the root causes for failures similar to how prior executions
> are stored in the {{ExecutionVertex}} using the {{EvictingBoundedList}} and
> then serve this information via the Web UI.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
