You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flink.apache.org by "Robert Metzger (Jira)" <ji...@apache.org> on 2021/09/01 15:05:00 UTC
[jira] [Created] (FLINK-24114) Make
CompletedOperationCache.COMPLETED_OPERATION_RESULT_CACHE_DURATION_SECONDS
configurable (at least for savepoint trigger operations)
Robert Metzger created FLINK-24114:
--------------------------------------
Summary: Make CompletedOperationCache.COMPLETED_OPERATION_RESULT_CACHE_DURATION_SECONDS configurable (at least for savepoint trigger operations)
Key: FLINK-24114
URL: https://issues.apache.org/jira/browse/FLINK-24114
Project: Flink
Issue Type: Improvement
Components: Runtime / Coordination
Affects Versions: 1.15.0
Reporter: Robert Metzger
Currently, it can happen that external services triggering savepoints can not persist the savepoint location from the savepoint handler, because the operation cache has a hardcoded value of 5 minutes, until entries (which have been accessed at least once) are evicted.
To avoid scenarios where the savepoint location has been accessed, but the external system failed to persist the location, I propose to make this eviction timeout configurable (so that I as a user can configure a value of 24 hours for the cache eviction).
(This is related to FLINK-24113)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)