[
https://issues.apache.org/jira/browse/FLINK-24114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17408749#comment-17408749
]
Robert Metzger commented on FLINK-24114:
----------------------------------------
True, I could query it from the checkpoints endpoint. However, this is
indicates that the /savepoint endpoints are semantically broken: Why do I
trigger & poll against the /savepoint endpoint, and then retrieve the final
result from the /checkpoints endpoint? (and there from a list of checkpoints I
guess?).
> 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)
