[
https://issues.apache.org/jira/browse/FLINK-32806?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17776630#comment-17776630
]
Samrat Deb commented on FLINK-32806:
------------------------------------
Thank you [~mapohl] for your view.
I am alligned with keeping default time-to-live at infinity/max to align with
the current behavior. I will add configuration param to make this configurable.
> The memory footprint of the entry is still quite small. I'm wondering whether
> we should keep this in the backlog for the sake of not letting the
> configuration grow even more. WDYT?
In our EMR cluster, we've observed this scenario occurring just once in the
past year, and it was specific to a long-running cluster for certain Cx. Given
this, it seems reasonable to keep it in the backlog for the time being. If the
need for this feature arises in the future, we can certainly revisit it and
incorporate it.
I'll proceed with working on the patch and will request your review within the
next couple of days. :)
> 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)
