[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987592#comment-16987592
]
Yadong Xie commented on FLINK-14717:
------------------------------------
Hi [~lining] and [~chesnay]
I think the key to solving the problem is providing data sorting, filtering and
paging capabilities in the rest API.
It would be much more user-friendly if users can search/sort the exception data
rather than expending lots of levels.
I wonder if we could change the exception limit size to the page size of the
pagination, and make `vertex name` and `subtask id` searchable in the rest API,
the sort capability for the exception time is also necessary.
what do you think about it?
> JobExceptionsHandler show exceptions of prior attempts
> --------------------------------------------------------
>
> Key: FLINK-14717
> URL: https://issues.apache.org/jira/browse/FLINK-14717
> Project: Flink
> Issue Type: Sub-task
> Components: Runtime / Web Frontend
> Reporter: lining
> Priority: Major
> Attachments: screenshot-1.png
>
>
> *Current*
> The job's exceptions just show current attempt’s exceptions in web UI.(ps:
> [code|https://github.com/apache/flink/blob/34b5399f4effb679baabd8bca312cbf92ec34165/flink-runtime/src/main/java/org/apache/flink/runtime/rest/handler/job/JobExceptionsHandler.java#L97-L98])
> If the job failovers, we couldn't see any prior attempts' exceptions.
> *Proposal*
> We could use executionVertex.getPriorExecutionAttempt to get prior attempt in
> JobExceptionsHandler.
> {code:java}
> for (int i = task.getAttemptNumber() - 1; i >= 0; i--) {
> task = executionVertex.getPriorExecutionAttempt(i);
> }
> {code}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
