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

• Type: Bug
• Status: Closed
• Priority: Blocker
• Resolution: Fixed
• Affects Version/s: 1.10.0, 1.11.0
• Fix Version/s: 1.10.0
• Component/s: Runtime / State Backends
• Labels: pull-request-available
• Assignee: Yu Li
• Reporter: Yun Tang
• Created: 24/Dec/19 03:24
• Updated: 07/Jan/20 19:02
• Resolved: 07/Jan/20 19:02

Description

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.

Issue Links

• is related to: FLINK-15368 Add end-to-end test for controlling RocksDB memory usage
• links to: GitHub Pull Request #10670