[
https://issues.apache.org/jira/browse/FLINK-15938?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031593#comment-17031593
]
Benchao Li commented on FLINK-15938:
------------------------------------
[~liyu] I just noticed that background cleanup is enabled default in 1.10.
We are using 1.9.0 now, are see constantly heap oom for a simple inner join.
> Idle state not cleaned in StreamingJoinOperator and
> StreamingSemiAntiJoinOperator
> ---------------------------------------------------------------------------------
>
> Key: FLINK-15938
> URL: https://issues.apache.org/jira/browse/FLINK-15938
> Project: Flink
> Issue Type: Improvement
> Components: Table SQL / Planner
> Affects Versions: 1.9.2, 1.10.0
> Reporter: Benchao Li
> Priority: Critical
>
> {code:java}
> return StateTtlConfig
> .newBuilder(Time.milliseconds(retentionTime))
> .setUpdateType(StateTtlConfig.UpdateType.OnCreateAndWrite)
>
> .setStateVisibility(StateTtlConfig.StateVisibility.ReturnExpiredIfNotCleanedUp)
> .build();
> {code}
> StateTtl is constructed in above code for `StreamingJoinOperator` and
> `StreamingSemiAntiJoinOperator`.
> However, as stated in
> [https://ci.apache.org/projects/flink/flink-docs-master/dev/stream/state/state.html#cleanup-of-expired-state]
> , the state will be cleaned only when it's read which means the state will
> not be cleaned enless we read it.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
