Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
Description
Flink history server stores information for an unlimited number of completed jobs, which is inconvenient to dig through on long-running instances and might cause performance degradation in the long run.
Spark for example addresses this issue by limiting the number of jobs to keep by a configuration parameter spark.history.retainedApplications with a default of 50 jobs to keep.
Introducing a similar configuration option to the Flink history server would improve the usability and performability of long-running history server instances.
Attachments
Issue Links
- relates to
-
FLINK-11963 Add time-based cleanup mechanism in history server
- Closed
- supercedes
-
FLINK-11963 Add time-based cleanup mechanism in history server
- Closed
- links to