[jira] [Updated] (FLINK-10198) Set Env object in DBOptions for RocksDB

["Flink Jira Bot (Jira)" <ji...@apache.org>]

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

Flink Jira Bot updated FLINK-10198:
-----------------------------------
    Labels: auto-unassigned pull-request-available stale-major  (was: auto-unassigned pull-request-available)

I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help the community manage its development. I see this issues has been marked as Major but is unassigned and neither itself nor its Sub-Tasks have been updated for 30 days. I have gone ahead and added a "stale-major" to the issue". If this ticket is a Major, please either assign yourself or give an update. Afterwards, please remove the label or in 7 days the issue will be deprioritized.


> Set Env object in DBOptions for RocksDB
> ---------------------------------------
>
>                 Key: FLINK-10198
>                 URL: https://issues.apache.org/jira/browse/FLINK-10198
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>    Affects Versions: 1.7.0
>            Reporter: Stefan Richter
>            Priority: Major
>              Labels: auto-unassigned, pull-request-available, stale-major
>
> 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
(v8.3.4#803005)