[
https://issues.apache.org/jira/browse/FLINK-14717?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16987622#comment-16987622
]
lining commented on FLINK-14717:
--------------------------------
The problem now is to keep the system stable in case of information overload,
while allowing users to view the data they want to see.
First, it is reasonable to add sorting, which solves the priority problem.
Secondly, pagination, return the count of exceptions and change the current
limit to the page size. So that the user needn't to continuously increase the
limit to see more exceptions as won't know the total of exceptions.
Third, filtering, users can quickly find the information they want to see. The
filter conditions here could be time、 vertex name.
> 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)
