[
https://issues.apache.org/jira/browse/FLINK-6766?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16031085#comment-16031085
]
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_r119344563
--- Diff: docs/ops/state_backends.md ---
@@ -88,6 +102,13 @@ that is (per default) stored in the TaskManager data
directories. Upon checkpoin
RocksDB data base will be checkpointed into the configured file system and
directory. Minimal
metadata is stored in the JobManager's memory (or, in high-availability
mode, in the metadata checkpoint).
+The RocksDBStateBackend always performs asynchronous snapshots.
+
+Limitations of the RocksDBStateBackend:
+
+ - As RocksDB's JNI bridge API is based on byte[], the maximum supported
size per key and per value is 2^31 bytes each.
+ IMPORTANT: states that use merge operations in RocksDB (e.g. ListState)
can silently accumulate value sizes > 2^31 bytes and will then fail on their
next retrival. This is currently a limitation of RocksDB JNI.
+
--- End diff --
retrieval
> 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)
