StefanRRichter commented on a change in pull request #8185: [FLINK-12212] [docs] clarify that operator state is checkpointed asynchronously URL: https://github.com/apache/flink/pull/8185#discussion_r276245387
########## File path: docs/ops/state/large_state_tuning.md ########## @@ -100,22 +100,18 @@ number of network buffers used per outgoing/incoming channel is limited and thus may be configured without affecting checkpoint times (see [network buffer configuration](../config.html#configuring-the-network-buffers)). -## Make state checkpointing Asynchronous where possible +## Asynchronous Checkpointing When state is *asynchronously* snapshotted, the checkpoints scale better than when the state is *synchronously* snapshotted. -Especially in more complex streaming applications with multiple joins, Co-functions, or windows, this may have a profound +Especially in more complex streaming applications with multiple joins, co-functions, or windows, this may have a profound impact. -To get state to be snapshotted asynchronously, applications have to do two things: +For state to be snapshotted asynchronsously, you need to use a state backend which supports asynchronous snapshotting. +Starting from Flink 1.3, both RocksDB-based as well as heap-based state backends (`filesystem`) support asynchronous +snapshotting and use it by default. This applies to to both managed operator state as well as managed keyed state. Review comment: We don't talk about timer state here or do you count that under "keyed"? ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
