You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While in tikv, we only support set max_background_jobs and max_background_flushes, and then calculate max_background_compactions by max_background_jobs - max_background_flushes. But in DBConfigManager, max_background_compactions is not updated when max_background_jobs or max_background_flushes changes.
What did you expect?
What did happened?
The text was updated successfully, but these errors were encountered:
Bug Report
What version of TiKV are you using?
What operating system and CPU are you using?
Steps to reproduce
rocksdb uses
max_background_flushes
andmax_background_compactions
to control the background thread pool size, see:https://github.com/tikv/rocksdb/blob/fe76937087f81e95a323bbf00fcd109c7b39c649/db/db_impl/db_impl_compaction_flush.cc#L2582-L2605
While in tikv, we only support set
max_background_jobs
andmax_background_flushes
, and then calculatemax_background_compactions
bymax_background_jobs - max_background_flushes
. But inDBConfigManager
,max_background_compactions
is not updated whenmax_background_jobs
ormax_background_flushes
changes.What did you expect?
What did happened?
The text was updated successfully, but these errors were encountered: