You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "zhijiang (Jira)" <ji...@apache.org> on 2019/12/24 03:56:00 UTC
[jira] [Assigned] (FLINK-15370) Configured write buffer manager
actually not take effect in RocksDB's DBOptions
[ https://issues.apache.org/jira/browse/FLINK-15370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
zhijiang reassigned FLINK-15370:
--------------------------------
Assignee: Yu Li
> Configured write buffer manager actually not take effect in RocksDB's DBOptions
> -------------------------------------------------------------------------------
>
> Key: FLINK-15370
> URL: https://issues.apache.org/jira/browse/FLINK-15370
> Project: Flink
> Issue Type: Bug
> Components: Runtime / State Backends
> Affects Versions: 1.10.0, 1.11.0
> Reporter: Yun Tang
> Assignee: Yu Li
> Priority: Blocker
> Fix For: 1.10.0, 1.11.0
>
>
> Currently, we call {{DBOptions#setWriteBufferManager}} after we extract the {{DBOptions}} from {{RocksDBResourceContainer}}, however, we would extract a new {{DBOptions}} when creating the RocksDB instance. In other words, the configured write buffer manager would not take effect in the {{DBOptions}} which finally used in target RocksDB instance.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)