[jira] [Closed] (FLINK-15917) Root Exception not shown in Web UI

["Gary Yao (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-15917?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Yao closed FLINK-15917.
----------------------------
    Resolution: Fixed

> Root Exception not shown in Web UI
> ----------------------------------
>
>                 Key: FLINK-15917
>                 URL: https://issues.apache.org/jira/browse/FLINK-15917
>             Project: Flink
>          Issue Type: Bug
>          Components: Runtime / Coordination
>    Affects Versions: 1.9.2, 1.10.0
>            Reporter: Gary Yao
>            Assignee: Gary Yao
>            Priority: Critical
>             Fix For: 1.10.0
>
>
> *Description*
>  On the job details page in the Exceptions → Root Exception tab, exceptions that cause the job to restart are not displayed.
>  This is already a problem since 1.9.0 if {{jobmanager.execution.failover-strategy: region}} is configured,
>  which we do in the default flink-conf.yaml.
> *Workarounds*
>  Users that run into this problem can set {{jobmanager.scheduler: legacy}} and unset {{jobmanager.execution.failover-strategy}} in their {{flink-conf.yaml}}
> *How to reproduce*
>  In {{flink-conf.yaml}} set {{restart-strategy: fixed-delay}} so enable job restarts.
> {noformat}
> $ bin/start-cluster.sh
> $ bin/flink run -d examples/streaming/TopSpeedWindowing.jar
> $ bin/taskmanager.sh stop
> {noformat}
> Assert that no exception is displayed in the Web UI.
> *Expected behavior*
>  The stacktrace of the exception should be displayed. Whether the exception should be also shown if only a partial region of the job failed is up for discussion.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)