[
https://issues.apache.org/jira/browse/FLINK-32806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18119859#comment-18119859
]
william commented on FLINK-32806:
---------------------------------
I've opened a PR for this: https://github.com/apache/flink/pull/29304
It follows the direction discussed above: no eviction at all unless
job-result-store.clean-job-result.ttl is configured (so the current behaviour
stays the
default), and the real Configuration is now wired through AbstractNonHaServices
and
StandaloneHaServices so that the option actually takes effect.
Happy to adjust the approach if you would prefer something different.
> EmbeddedJobResultStore keeps the non-dirty job entries forever
> --------------------------------------------------------------
>
> Key: FLINK-32806
> URL: https://issues.apache.org/jira/browse/FLINK-32806
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / Coordination
> Affects Versions: 1.18.0, 1.17.1, 1.19.0
> Reporter: Matthias Pohl
> Assignee: hk__lrzy
> Priority: Major
> Labels: pull-request-available, stale-assigned, starter
>
> The {{EmbeddedJobResultStore}} keeps the entries of cleaned-up jobs in-memory
> forever. We might want to add a TTL to have those entries be removed after a
> certain amount of time to allow maintaining the memory footprint of the
> {{EmbeddedJobResultStore}}.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
