Details
-
Sub-task
-
Status: Closed
-
Blocker
-
Resolution: Fixed
-
1.5.0
Description
In order to serve the JobExecutionResults we have to cache them in the Dispatcher after the JobManagerRunner has finished. The cache should have a configurable size and should periodically clean up stale entries in order to avoid memory exhaustion.
Attachments
Issue Links
- is depended upon by
-
FLINK-8233 Expose JobExecutionResult via HTTP
- Closed
- relates to
-
FLINK-8300 Make JobExecutionResult accessible in per-job cluster mode
- Closed
- links to