You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "Flink Jira Bot (Jira)" <ji...@apache.org> on 2021/05/20 10:53:02 UTC
[jira] [Closed] (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 ]
Flink Jira Bot closed FLINK-12486.
----------------------------------
Resolution: Auto Closed
This issue was labeled "stale-minor" 7 ago and has not received any updates so I have gone ahead and closed it. If you are still affected by this or would like to raise the priority of this ticket please re-open, removing the label "auto-closed" and raise the ticket priority accordingly.
> 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)