[jira] [Commented] (FLINK-17998) Support limiting job history size

["miracle (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLINK-17998?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259539#comment-17259539 ] 

miracle commented on FLINK-17998:
---------------------------------

Why not use days instead of numbers?

In my company, the number of days is controlled by default, and the tasks beyond two days will be deleted. In this way, the total number of tasks controlled is about 2,000, and the page can hold .

> Support limiting job history size
> ---------------------------------
>
>                 Key: FLINK-17998
>                 URL: https://issues.apache.org/jira/browse/FLINK-17998
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Configuration
>            Reporter: Daniel Laszlo Magyar
>            Assignee: Daniel Laszlo Magyar
>            Priority: Minor
>              Labels: pull-request-available
>             Fix For: 1.12.0
>
>
> 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|https://spark.apache.org/docs/2.2.0/monitoring.html#spark-configuration-options] {{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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)