Skip to content
Open
Changes from 2 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions docs/content/docs/ops/state/state_backends.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ Out of the box, Flink bundles these state backends:

- *HashMapStateBackend*
- *EmbeddedRocksDBStateBackend*
- *ForStStateBackend*

If nothing else is configured, the system will use the HashMapStateBackend.

Expand Down Expand Up @@ -95,7 +96,7 @@ Certain RocksDB native metrics are available but disabled by default, you can fi

The total memory amount of RocksDB instance(s) per slot can also be bounded, please refer to documentation [here]({{< ref "docs/ops/state/large_state_tuning" >}}#bounding-rocksdb-memory-usage) for details.

## The ForStStateBackend
### The ForStStateBackend
Comment thread
Dennis-Mircea marked this conversation as resolved.

The *ForStStateBackend* is a state backend that is based on [ForSt project](https://github.com/ververica/ForSt),
which is also a LSM-tree structured key-value store and built on top of the RocksDB.
Expand Down Expand Up @@ -299,7 +300,7 @@ See [configuration docs]({{< ref "docs/deployment/config" >}}#rocksdb-native-met
Enabling RocksDB's native metrics may have a negative performance impact on your application.
{{< /hint >}}

### Advanced RocksDB Memory Turning
### Advanced RocksDB Memory Tuning

{{< hint info >}}
Flink offers sophisticated default [memory management for RocksDB](#memory-management) that should work for most use-cases. The below mechanisms should mainly be used for *expert tuning* or *trouble shooting*.
Expand Down