Stefan Richter created FLINK-10198:
--------------------------------------
Summary: Set Env object in DBOptions for RocksDB
Key: FLINK-10198
URL: https://issues.apache.org/jira/browse/FLINK-10198
Project: Flink
Issue Type: Improvement
Affects Versions: 1.7.0
Reporter: Stefan Richter
Assignee: Stefan Richter
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.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
