Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-21935

Remove "state.backend.async" option.

    XMLWordPrintableJSON

    Details

    • Release Note:
      Hide
      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.
      Show
      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.

      Description

      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 Seth Wiesman and Yu Li

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                sewen Stephan Ewen
                Reporter:
                sewen Stephan Ewen
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: