You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Márton Balassi (Jira)" <ji...@apache.org> on 2020/05/28 14:14:00 UTC

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

     [ https://issues.apache.org/jira/browse/FLINK-17998?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Márton Balassi reassigned FLINK-17998:
--------------------------------------

    Assignee: Daniel Laszlo Magyar

> 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
>
> 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)