[
https://issues.apache.org/jira/browse/FLINK-12476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Zagrebin updated FLINK-12476:
------------------------------------
Release Note: The background cleanup for state with time-to-live can be
enabled with the method StateTtlConfig#cleanupInBackground() now. If the state
backend supports the background cleanup, the default strategy will kick in.
(was: StateTtlConfig can now be created with the method cleanupInBackground().)
> [State TTL] Consider setting a default background cleanup strategy in
> StateTtlConfig
> ------------------------------------------------------------------------------------
>
> Key: FLINK-12476
> URL: https://issues.apache.org/jira/browse/FLINK-12476
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Affects Versions: 1.8.0
> Reporter: Andrey Zagrebin
> Assignee: vinoyang
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.8.0, 1.9.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> At the moment we have two efficient background cleanup strategies:
> incremental for heap and compaction filter for RocksDB. *StateTtlConfig* has
> 2 methods to activate them: *cleanupIncrementally* and
> *cleanupInRocksdbCompactFilter*. Each is activated only for certain backend
> type and inactive for other. They have different tuning parameters.
> The idea is to add method *cleanupInBackground* which would activate default
> background cleanup. User does not need to think then about details or used
> backend if not needed. Depending on actually used backend, the corresponding
> cleanup will kick in. If original strategy is not set with
> *cleanupIncrementally* and *cleanupInRocksdbCompactFilter* then backends
> should check whether default background cleanup is activated and if so, use
> it with default parameters.
> We can also deprecate the parameterless *cleanupInRocksdbCompactFilter()* in
> favour of this new method.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
