Status

Current state: [Under Discussion]

Discussion thread: http://apache-flink-mailing-list-archive.1008284.n3.nabble.com/DISCUSS-FLIP-75-Flink-Web-UI-Improvement-Proposal-td33540.html

JIRA: https://issues.apache.org/jira/browse/FLINK-14127

Released: <Flink Version>

Please keep the discussion on the mailing list rather than commenting on the wiki (wiki discussions get unwieldy fast).

Motivation

According to the current code, 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.

Proposed Changes

Making the MAX_NUMBER_EXCEPTION_TO_REPORT configurable in REST API can solve this problem.

Frontend Design

Add a load more button in the exception history page, when there the exception count is more than 20(the truncated is true), clicking the load more button the frontend will add 20 to the MAX_NUMBER_EXCEPTION_TO_REPORT request params.

REST API Design

Add max exceptions query parameter. FLINK-11405