davidradl commented on code in PR #28094: URL: https://github.com/apache/flink/pull/28094#discussion_r3196216595
########## docs/content/docs/ops/state/state_backends.md: ########## @@ -55,8 +55,8 @@ that store the values, triggers, etc. The HashMapStateBackend is encouraged for: - - Jobs with large state, long windows, large key/value states. - - All high-availability setups. + - Jobs whose state fits comfortably in the JVM heap of the TaskManagers, where fast, in-memory state access is the priority. + - Jobs with low-latency requirements that benefit from avoiding de-/serialization on every state access. Review Comment: I assume the main consideration is the lack of recoverability compared to RocksDB. I think we should mention the recoverability considerations here. Maybe in a section similar to the RocksDB section "Limitations of the " -- 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. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
