[ 
https://issues.apache.org/jira/browse/FLINK-25163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17453766#comment-17453766
 ] 

Yun Tang edited comment on FLINK-25163 at 12/6/21, 3:34 AM:
------------------------------------------------------------

The methods of {{setMaxBackgroundFlushes}} and {{setMaxBackgroundCompactions}} 
have been tagged as deprecated to use {{setMaxBackgroundJobs}} instead (see 
https://github.com/facebook/rocksdb/pull/2908). we could drop the usage of 
{{setIncreaseParallelism}} in Flink to use {{setMaxBackgroundJobs}} instead.

[~liufangqi] WDYT?


was (Author: yunta):
The methods of {{setMaxBackgroundFlushes}} and {{setMaxBackgroundCompactions}} 
have been tagged as deprecated to use {{setMaxBackgroundJobs}} instead (see 
https://github.com/facebook/rocksdb/pull/2908). we could drop the usage of 
{{setIncreaseParallelism}} in Flink to use {{setMaxBackgroundJobs}} instead.

> Add more options for rocksdb state backend to make configuration more flexible
> ------------------------------------------------------------------------------
>
>                 Key: FLINK-25163
>                 URL: https://issues.apache.org/jira/browse/FLINK-25163
>             Project: Flink
>          Issue Type: Improvement
>          Components: Runtime / State Backends
>            Reporter: 刘方奇
>            Priority: Major
>
> Now flink has less options than the configurations what Rocksdb can set. We 
> can see many function in the org.rocksdb.DBOptions that can influence its 
> behavior(e.g rocksdb background threads).
> It make us do less when we want to do some thing to tuning Rocksdb. In my 
> opinion, there are at least there options:
>  # maxBackgroundFlushes, it can define the background flush threads. default 
> 1.
>  # maxBackgroundCompactions, it can define the background compaction threads. 
> default 1.
>  # maxBackgroundJobs, it can define the background threads. default 2.
> setIncreaseParallelism (the most we can do for the rocksdb backend background 
> threads) seems like can do little. It can't change the flush threads. I think 
> it's necessary to make rocksdb configuration flexible.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to