You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Till Rohrmann (Jira)" <ji...@apache.org> on 2019/09/25 08:09:00 UTC

[jira] [Assigned] (FLINK-14180) Enable config of maximum capacity of FileArchivedExecutionGraphStore.

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

Till Rohrmann reassigned FLINK-14180:
-------------------------------------

    Assignee: Yingjie Cao

> Enable config of maximum capacity of FileArchivedExecutionGraphStore.
> ---------------------------------------------------------------------
>
>                 Key: FLINK-14180
>                 URL: https://issues.apache.org/jira/browse/FLINK-14180
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / Coordination
>            Reporter: Yingjie Cao
>            Assignee: Yingjie Cao
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> Currently, Flink session cluster uses FileArchivedExecutionGraphStore to keep finished jobs for historic requests. The FileArchivedExecutionGraphStore purges archived ExecutionGraphs only by an expiration time. In a session cluster on which runs many batch jobs, it is hard to config the jobstore.expiration-time, if configured too short, the historical information may have been deleted when the user want to check it, and if configured too long, the web front end may response very slowly when the number of finished job is too large. We'd better add a new config option to allow config of the maximum capacity of the FileArchivedExecutionGraphStore, which is well supported by Guava Cache. Then we can set the expiration time to a relative long value and set the maximum capacity to an appropriate value which does not make the web ui become too slow.



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