You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Konstantin Knauf (Jira)" <ji...@apache.org> on 2021/07/29 07:30:12 UTC
[jira] [Reopened] (FLINK-12486) RocksDB State Backend docs don't
explain that operator state is kept on heap
[ https://issues.apache.org/jira/browse/FLINK-12486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konstantin Knauf reopened FLINK-12486:
--------------------------------------
Re-opening in accordance with https://issues.apache.org/jira/browse/FLINK-23206.
> RocksDB State Backend docs don't explain that operator state is kept on heap
> ----------------------------------------------------------------------------
>
> Key: FLINK-12486
> URL: https://issues.apache.org/jira/browse/FLINK-12486
> Project: Flink
> Issue Type: Improvement
> Components: Documentation, Runtime / State Backends
> Affects Versions: 1.7.2, 1.8.0, 1.9.0
> Reporter: Fabian Hueske
> Assignee: Aitozi
> Priority: Minor
> Labels: auto-closed, pull-request-available, stale-assigned
> Time Spent: 10m
> Remaining Estimate: 0h
>
> The documentation of theĀ [RocksDB State Backend|https://ci.apache.org/projects/flink/flink-docs-release-1.8/ops/state/state_backends.html#the-rocksdbstatebackend] does not explain that operator state is maintained on the JVM heap and not in RocksDB (on disk).
--
This message was sent by Atlassian Jira
(v8.3.4#803005)