Details
-
Bug
-
Resolution: User Error
-
Major
-
master
-
None
-
5.1.0-1335
-
Untriaged
-
Centos 64-bit
-
Yes
Description
I am trying to tune the following RocksDB settings via diag eval:
backend=rocksdb
rocksdb_cf_options=write_buffer_size=2097152,max_write_buffer_number=1
rocksdb_options=max_background_jobs=1
kv-engine successfully receives my requests:
2017-10-24T15:37:57.609308-07:00 NOTICE (bucket-1) EPEngine::initialize: using configuration:"ht_locks=47;max_size=53687091200;dbname=/data/bucket-1;backend=couchdb;couch_bucket=bucket-1;max_vbuckets=128;alog_path=/data/bucket-1/access.log;data_traffic_enabled=false;max_num_workers=3;uuid=9b59e99b358191c385e1b224be5a2e46;conflict_resolution_type=seqno;bucket_type=persistent;item_eviction_policy=full_eviction;failpartialwarmup=false;backend=rocksdb;rocksdb_cf_options=write_buffer_size=2097152,max_write_buffer_number=1;rocksdb_options=max_background_jobs=1"
|
However, max_write_buffer_number doesn't seem to be applied:
# grep "write_buffer_size" /data/bucket-1/rocksdb.0/OPTIONS-000010
|
db_write_buffer_size=0
|
write_buffer_size=2097152
|
write_buffer_size=2097152
|
write_buffer_size=2097152
|
|
|
# grep "max_write_buffer_number" /data/bucket-1/rocksdb.0/OPTIONS-000010
|
max_write_buffer_number=2
|
max_write_buffer_number_to_maintain=0
|
max_write_buffer_number=2
|
max_write_buffer_number_to_maintain=0
|
max_write_buffer_number=2
|
|
|
# grep "max_background_jobs" /data/bucket-1/rocksdb.0/OPTIONS-000010
|
max_background_jobs=1
|