[
https://issues.apache.org/jira/browse/FLINK-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031087#comment-16031087
]
ASF GitHub Bot commented on FLINK-6766:
---------------------------------------
Github user alpinegizmo commented on a diff in the pull request:
https://github.com/apache/flink/pull/4011#discussion_r119344251
--- Diff: docs/monitoring/large_state_tuning.md ---
@@ -138,6 +138,22 @@ Unfortunately, RocksDB's performance can vary with
configuration, and there is l
RocksDB properly. For example, the default configuration is tailored
towards SSDs and performs suboptimal
on spinning disks.
+**Incremental Checkpoints**
+
+Incremental checkpoints can dramatically reduce the checkpointing time in
comparison to full checkpoints, at the cost of a (potentially) longer
+recovery time. The core idea is that incremental checkpoints only record
all changes to the previous completed checkpoint, instead of
+producing a full, self-contained backups of the backend. Like this,
incremental checkpoints build upon previous checkpoints. Flink leverages
--- End diff --
a full, self-contained backup of the state backend
> Update documentation with async backends and incremental checkpoints
> --------------------------------------------------------------------
>
> Key: FLINK-6766
> URL: https://issues.apache.org/jira/browse/FLINK-6766
> Project: Flink
> Issue Type: Improvement
> Components: State Backends, Checkpointing
> Reporter: Stefan Richter
> Assignee: Stefan Richter
> Fix For: 1.4.0
>
>
> This PR introduces some documentation about async heap backends and
> incremental snapshots with RocksDB.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
