[jira] [Commented] (FLINK-24114) Make CompletedOperationCache.COMPLETED_OPERATION_RESULT_CACHE_DURATION_SECONDS configurable (at least for savepoint trigger operations)

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

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

Chesnay Schepler commented on FLINK-24114:
------------------------------------------

I don't quite understand why this would be required if you have FLINK-24113.

If you manually shut down the cluster via the REST API, then after a stop-with-savepoint you can just wait for the job to terminate, and then query the savepoint location via the checkpoints endpoint.

Irrespective of whether it generally makes sense to make this parameter configurable, it doesn't seem required for your use-case.

> 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
>            Priority: Major
>
> 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)