Myasuka commented on a change in pull request #8441: [FLINK-12486][doc]clarify
the storage of operator state and broadcast state individually
URL: https://github.com/apache/flink/pull/8441#discussion_r322327941
##########
File path: docs/ops/state/state_backends.md
##########
@@ -123,6 +123,8 @@ RocksDBStateBackend is currently the only backend that
offers incremental checkp
Certain RocksDB native metrics are available but disabled by default, you can
find full documentation [here]({{ site.baseurl
}}/ops/config.html#rocksdb-native-metrics)
+**Attention:** No matter which backend is used, the [operator
state](../../dev/stream/state/state.html#operator-state) and [broadcast
state](../../dev/stream/state/broadcast_state.html) are all stored on JVM heap,
the different store locations mentioned above are scoped to
[keyedState]((../../dev/stream/state/state.html#keyed-state)).
Review comment:
Apart from the link location problem, I think we should only clarify that
even rocksDB state backend is configured, `operator state` and `broadcast
state` are all stored in JVM heap as this part belongs to the rocksdb session
of documentation.
----------------------------------------------------------------
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
