[
https://issues.apache.org/jira/browse/FLINK-32806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17772940#comment-17772940
]
Samrat Deb commented on FLINK-32806:
------------------------------------
Hi [~mapohl] ,
I have a couple of questions regarding the proposed change:
# Could you please clarify what the default time-to-live (TTL) for the entries
will be? Additionally, are we considering exposing any configuration options
for TTL, or is it best to avoid adding more configuration complexity?
# Are we exploring any other conditions for removing an entry, apart from
time-based removal? For example, should we also consider removing entries when
the map size exceeds a certain threshold to prevent excessive memory
consumption?
I'd appreciate your insights on these points.
> 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: 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)
