[
https://issues.apache.org/jira/browse/FLINK-15507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238551#comment-17238551
]
Zakelly Lan commented on FLINK-15507:
-------------------------------------
I'm glad we bring this into discussion again.
There is one thing I want to make sure. Are we making local recovery activated
for all state backends or only for RocksDB? FsStateBackend does not benefit as
much as RocksDB with incremental snapshot. Since there is only a single config
named ```state.backend.local-recovery``` for now, if we active local recovery
only for RocksDB, there are two options:
# Introduce a local-recovery configuration for each state backend, such as
```state.backend.rocksdb.local-recovery```.
# Behave differently for different state backends whenÂ
```state.backend.local-recovery``` is not set.
I prefer the latter. The configuration is more clear but it may bring some
confusion in default behavior. Or we just activate it for all backends and the
FsStateBackend will occupy more local disk space.
> Activate local recovery for RocksDB backends by default
> -------------------------------------------------------
>
> Key: FLINK-15507
> URL: https://issues.apache.org/jira/browse/FLINK-15507
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: Stephan Ewen
> Assignee: Zakelly Lan
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> For the RocksDB state backend, local recovery has no overhead when
> incremental checkpoints are used.
> It should be activated by default, because it greatly helps with recovery.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
