[FLINK-10198] Set Env object in DBOptions for RocksDB

• Type: Improvement
• Status: Open
• Priority: Not a Priority
• Resolution: Unresolved
• Affects Version/s: 1.7.0
• Component/s: Runtime / State Backends
• Labels: auto-deprioritized-major auto-deprioritized-minor auto-unassigned pull-request-available
• Assignee: Unassigned
• Reporter: Stefan Richter
• Created: 22/Aug/18 13:53
• Updated: 27/Dec/21 22:38

Description

I think we should consider to always set a default environment when we create the DBOptions.

See https://github.com/facebook/rocksdb/wiki/rocksdb-basics:
Support for Multiple Embedded Databases in the same process
A common use-case for RocksDB is that applications inherently partition their data set into logical partitions or shards. This technique benefits application load balancing and fast recovery from faults. This means that a single server process should be able to operate multiple RocksDB databases simultaneously. This is done via an environment object named Env. Among other things, a thread pool is associated with an Env. If applications want to share a common thread pool (for background compactions) among multiple database instances, then it should use the same Env object for opening those databases.

Similarly, multiple database instances may share the same block cache.

Issue Links

• links to: GitHub Pull Request #6603