[
https://issues.apache.org/jira/browse/FLINK-11139?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719734#comment-16719734
]
Fabian Hueske commented on FLINK-11139:
---------------------------------------
[~zhaoshijie], I assume you configured a [idle state retention
time|https://ci.apache.org/projects/flink/flink-docs-release-1.7/dev/table/streaming/query_configuration.html#idle-state-retention-time].
How did you choose the min and max values? The difference between min and max
determines how often a timer is registered.
Moreover, [~hequn8128] reworked the clean up timers such that they use the
timer delete feature that was added in Flink 1.6.0.
The PR was merged a few days ago and should already fix the problem.
> stream non window join support state ttl
> ----------------------------------------
>
> Key: FLINK-11139
> URL: https://issues.apache.org/jira/browse/FLINK-11139
> Project: Flink
> Issue Type: Improvement
> Components: Table API & SQL
> Affects Versions: 1.7.0
> Reporter: zhaoshijie
> Priority: Major
>
> stream non window join function use timer to delete expired data，it is ok for
> small amount of data or short expiration time，but it will be OOM（too many
> timer）on taskManger when there is a long expiration time and a large
> amount of data。In fact, table module other state function has same problem，I
> would like to contribute to fix it。
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
