[
https://issues.apache.org/jira/browse/FLINK-21935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephan Ewen resolved FLINK-21935.
----------------------------------
Release Note:
The 'state.backend.async' option is deprecated.
Snapshots are always asynchronous now (as they were by default before) and
there is no option to configure a synchronous snapshot any more.
The constructors of "FsStateBackend" and "MemoryStateBackend" that take a flag
for sync/async snapshots are kept for API compatibility, but the flags are
ignored now.
was:
Fixed in 1.13.0 via
- a31d0feae1ff7a9adc6dff1462f408fdb2e30037
- 1c1bf546e36f2d871f0abaf63024dd15657e79ca
Resolution: Fixed
Fixed in 1.13.0 via
- a31d0feae1ff7a9adc6dff1462f408fdb2e30037
- 1c1bf546e36f2d871f0abaf63024dd15657e79ca
> Remove "state.backend.async" option.
> ------------------------------------
>
> Key: FLINK-21935
> URL: https://issues.apache.org/jira/browse/FLINK-21935
> Project: Flink
> Issue Type: Improvement
> Components: Runtime / State Backends
> Reporter: Stephan Ewen
> Assignee: Stephan Ewen
> Priority: Blocker
> Labels: pull-request-available
> Fix For: 1.13.0
>
>
> Checkpoints are always asynchronous, there is no case ever for a synchronous
> checkpoint.
> The RocksDB state backend doesn't even support synchronous snapshots, and the
> HashMap Heap backend also has no good use case for synchronous snapshots
> (other than a very minor reduction in heap objects).
> Most importantly, we should not expose this option in the constructors of the
> new state backend API classes, like {{HashMapStateBackend}}.
> I marked this a blocker because it is part of the new user-facing State
> Backend API and I would like to avoid that this option enters this API and
> causes confusion when we eventually remove it.
> /cc [~sjwiesman] and [~liyu]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
