[jira] [Resolved] (FLINK-15370) Configured write buffer manager actually not take effect in RocksDB's DBOptions

["Stephan Ewen (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/FLINK-15370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephan Ewen resolved FLINK-15370.
----------------------------------
    Resolution: Fixed

Fixed in
  - 1.10.0 via {{6184922158b40d25ad42ae0ccb4abf579c9e7ff2}} and {{666c4562909c4512d1a0df51a0067ca7e577ab76}}
  - 1.11.0 via {{0b7d496f3ddb178dc2ad1333ffb692055006a210}} and {{6ff392842f9dc4d3c9c808e7912558d477826379}}

> 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
>              Labels: pull-request-available
>             Fix For: 1.10.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> 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)