[
https://issues.apache.org/jira/browse/FLINK-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16933969#comment-16933969
]
Yadong Xie edited comment on FLINK-11374 at 9/23/19 6:38 AM:
-------------------------------------------------------------
Hi [~trohrmann]
According to the current flink
[code|https://github.com/apache/flink/blob/34b5399f4effb679baabd8bca312cbf92ec34165/flink-runtime/src/main/java/org/apache/flink/runtime/rest/handler/job/JobExceptionsHandler.java#L54],
the MAX_NUMBER_EXCEPTION_TO_REPORT is default 20 and not configurable. The
problem is that the exception which is useful to users usually appears in the
first exception, but if there are a lot of exceptions happened, users can only
get the latest 20 exception messages, the first exception is gone.
Making the MAX_NUMBER_EXCEPTION_TO_REPORT configurable in the REST API can
solve this problem, and we can add filters(text or time-range) in the Web UI to
help users find useful exceptions.
What do you think about it?
was (Author: vthinkxie):
Hi [~trohrmann]
According to the current flink
[code|https://github.com/apache/flink/blob/34b5399f4effb679baabd8bca312cbf92ec34165/flink-runtime/src/main/java/org/apache/flink/runtime/rest/handler/job/JobExceptionsHandler.java#L54],
the MAX_NUMBER_EXCEPTION_TO_REPORT is default 20 and not configurable. The
problem is that the exception which is useful to users usually appears in the
first exception, but if there are a lot of exceptions happened, users can only
get the latest 20 exception messages, the first exception is gone.
Making the MAX_NUMBER_EXCEPTION_TO_REPORT configurable in flink-conf.yaml can
solve this problem, and we can add filters(text or time-range) in the Web UI to
help users find useful exceptions.
What do you think about it?
> See more failover and can filter by time range
> ----------------------------------------------
>
> Key: FLINK-11374
> URL: https://issues.apache.org/jira/browse/FLINK-11374
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / REST, Runtime / Web Frontend
> Reporter: lining
> Priority: Major
> Attachments: image-2019-01-22-11-40-53-135.png,
> image-2019-01-22-11-42-33-808.png
>
>
> Now failover just show limit size task failover latest time. If task has
> failed many time, we can not see the earlier time failover. Can we add filter
> by time to see failover which contains task attemp fail msg.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
