[jira] [Commented] (FLINK-6042) Display last n exceptions/causes for job restarts in Web UI

Wed, 29 Mar 2017 07:08:03 -0700 

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

ASF GitHub Bot commented on FLINK-6042:
---------------------------------------

GitHub user zentol opened a pull request:

    https://github.com/apache/flink/pull/3643

    [FLINK-6042] [web] Display exception history

    This is PR builds 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 16 (configurable) root exceptions.
    
    The history tab itself has up to 16 sub-tabs, one for each *job* attempt.
    
    We now also show the location and task name (which includes the subtask 
index) for the root exception.
    
    If no exception has occurred yet the page will look like this:
    
![after_1_1](https://cloud.githubusercontent.com/assets/5725237/24458394/199bbec8-1499-11e7-9e89-1f0944c86b8b.png)
    
    The latest tab when an exception has occurred:
    
![after_1_2](https://cloud.githubusercontent.com/assets/5725237/24458449/3bfd274a-1499-11e7-879b-706425e9777a.png)
    
    The history tab:
    
![after_1_3](https://cloud.githubusercontent.com/assets/5725237/24458463/484111ce-1499-11e7-9d40-e66ed9dfb17f.png)
    
    The history tab with a selected attempt:
    
![after_1_4](https://cloud.githubusercontent.com/assets/5725237/24458479/52d08aca-1499-11e7-8090-2188ef212663.png)
    
    The history tab growing over time; oldest exception is on the far right:
    
![after_1_5](https://cloud.githubusercontent.com/assets/5725237/24458499/65021bfa-1499-11e7-83dd-62381cb26552.png)
    
    The history tab when accessing a discarded exception:
    
![after_1_6](https://cloud.githubusercontent.com/assets/5725237/24458531/7cdf8e2e-1499-11e7-8cb7-ad337e45dc10.png)

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/3643.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 #3643
    
----
commit 03259065239689eb5718b9f67677a63b176b4e02
Author: zentol <ches...@apache.org>
Date:   2017-03-29T12:46:19Z

    [FLINK-6043] [web] Display exception timestamp

commit c2915979a0666c60f112d21d6761a9bd0d81f298
Author: zentol <ches...@apache.org>
Date:   2017-03-29T12:46:27Z

    Rebuild web-frontend

commit a8fab152eef92bc152a9a1ca6d045e442771f6cb
Author: zentol <ches...@apache.org>
Date:   2017-03-29T13:22:59Z

    +

commit c7ca6e40461282e946717d6d6897f23aed11c389
Author: zentol <ches...@apache.org>
Date:   2017-03-29T13:27:34Z

    ++

commit ff9d6ef77fc1fc36a7a05922aee7d83d97654f8a
Author: zentol <ches...@apache.org>
Date:   2017-03-28T13:18:26Z

    [FLINK-6042] Modify Web UI

commit 525c7a519fe51626a8a4e9750a8bf4d152262f68
Author: zentol <ches...@apache.org>
Date:   2017-03-28T13:18:46Z

    [FLINK-6042] Rebuild Web UI

commit 62aac50044fc1d17a46f6197c2a6e0f78b6a3ea9
Author: zentol <ches...@apache.org>
Date:   2017-03-28T13:56:27Z

    [FLINK-6024] Backend changes

----


> 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
>            Assignee: Chesnay Schepler
>
> 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)

Reply via email to