[
https://issues.apache.org/jira/browse/FLINK-29660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17623739#comment-17623739
]
LI Mingkun commented on FLINK-29660:
------------------------------------
Exception tab is also OK. But there are some deficiencies:
* It is not convenient for users to find the exception of specific subtask
* It can't provide root cause sometimes
In our batch case, there are many exceptions if we enable failover. It's
diffcult to identify the exception rootcause for a specific subTask.
If webUI shows all attmepts fo subtasks, we can jump into log of failed attemp,
and troubleshoot rootcause & slow case
> Show all attempts of subtasks in WebUI
> --------------------------------------
>
> Key: FLINK-29660
> URL: https://issues.apache.org/jira/browse/FLINK-29660
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Web Frontend
> Reporter: LI Mingkun
> Priority: Major
>
> Web UI only show subtask metric and TM log now.
> For batch jobs, It's very important to track the metric of fail attempt and
> jump into log stream of every attemp.
>
> Feature needed: enable expanded rows of all attempts for subtasks
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
