yeah, it's much better.
Then the questions are:
- Is it safe to disable WAL?
- Should we do that by default?
Thanks,
Igor.
On 22.08.2016 19:13, Somnath Roy wrote:
Igor,
I just verified setting 'disableWAL= true' in the ceph.conf rocksdb option and it is working as expected. I am not seeing any WAL traffic now.
Thanks & Regards
Somnath
-----Original Message-----
From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of Somnath Roy
Sent: Monday, August 22, 2016 8:53 AM
To: Igor Fedotov; ceph-devel
Subject: RE: Odd WAL traffic for BlueStore
disableWAL=true in the rocksdb option in ceph.conf or do this (if previous is buggy or not working)..
RocksDBStore::submit_transaction and RocksDBStore::submit_transaction_sync has this option set explicitly , make it 'true'.
woptions.disableWAL = true
Thanks & Regards
Somnath
-----Original Message-----
From: Igor Fedotov [mailto:ifedotov@xxxxxxxxxxxx]
Sent: Monday, August 22, 2016 8:12 AM
To: Somnath Roy; ceph-devel
Subject: Re: Odd WAL traffic for BlueStore
Can you point it out? Don't see any...
On 22.08.2016 18:08, Somnath Roy wrote:
Another point, I never tried but there is an option to disable WAL write during rocksdb write, we can try this option and see if that is reducing WAL partition writes or not.
Thanks & Regards
Somnath
-----Original Message-----
From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of Somnath Roy
Sent: Monday, August 22, 2016 8:06 AM
To: Igor Fedotov; ceph-devel
Subject: RE: Odd WAL traffic for BlueStore
Igor,
I am always seeing this WAL traffic in my 4k tests. Initially, I thought there are some faulty logic on Bluestore side and not honoring min_alloc_size , but, further debugging it seems the traffic is generated from BlueFS/Rocksdb.
Regarding rocksdb tuning, if you are not running the tests long enough (may be >20 min) you wouldn't be seeing any difference with default.
Thanks & Regards
Somnath
-----Original Message-----
From: ceph-devel-owner@xxxxxxxxxxxxxxx [mailto:ceph-devel-owner@xxxxxxxxxxxxxxx] On Behalf Of Igor Fedotov
Sent: Monday, August 22, 2016 6:47 AM
To: ceph-devel
Subject: Odd WAL traffic for BlueStore
Hi All,
While testing BlueStore as a standalone storage via FIO plugin I'm observing huge traffic to a WAL device.
Bluestore is configured to use 2 450 Gb Intel's SSD: INTEL SSDSC2BX480G4L
The first SSD is split into 2 partitions (200 & 250 Gb) for Block DB and Block WAL.
The second is split similarly and first 200Gb partition allocated for Raw Block data.
RocksDB settings are set as Somnath suggested in his 'RocksDB tuning' .
No much difference comparing to default settings though...
As a result when doing 4k sequential write (8Gb total) to a fresh storage I'm observing (using nmon and other disk mon tools) significant write traffic to WAL device. And it grows eventually from ~10Mbs to ~170Mbs. Raw Block device traffic is pretty stable at ~30 Mbs.
Additionally I inserted an output for BlueFS perf counters on umount(l_bluefs_bytes_written_wal & l_bluefs_bytes_written_sst).
The resulting values are very frustrating: ~28Gb and 4Gb for l_bluefs_bytes_written_wal & l_bluefs_bytes_written_sst respectively.
Doing 64K changes the picture dramatically:
WAL traffic is stable at 10-12 Mbs and RAW Block one is at ~400Mbs BlueFS counters are ~140Mb and 1K respectively.
Surely write completes much faster in the second case.
No WAL is reported in logs at BlueStore level for both cases.
High BlueFS WAL traffic is observed when running subsequent random 4K RW over the store propagated this way too.
I'm wondering why WAL device is involved in the process at all ( writes happen in min_alloc_size blocks) operate and why the traffic and written data volume is so high?
Don't we have some fault affecting 4K performance here?
Here are my settings and FIO job specification:
###########################
[global]
debug bluestore = 0/0
debug bluefs = 1/0
debug bdev = 0/0
debug rocksdb = 0/0
# spread objects over 8 collections
osd pool default pg num = 32
log to stderr = false
[osd]
osd objectstore = bluestore
bluestore_block_create = true
bluestore_block_db_create = true
bluestore_block_wal_create = true
bluestore_min_alloc_size = 4096
#bluestore_max_alloc_size = #or 4096
bluestore_fsck_on_mount = false
bluestore_block_path=/dev/sdi1
bluestore_block_db_path=/dev/sde1
bluestore_block_wal_path=/dev/sde2
enable experimental unrecoverable data corrupting features = bluestore rocksdb memdb
bluestore_rocksdb_options =
"max_write_buffer_number=16,min_write_buffer_number_to_merge=2,recycle_log_file_num=16,compaction_threads=32,flusher_threads=8,max_background_compactions=32,max_background_flushes=8,max_bytes_for_level_base=5368709120,write_buffer_size=83886080,level0_file_num_compaction_trigger=4,level0_slowdown_writes_trigger=400,level0_stop_writes_trigger=800"
rocksdb_cache_size = 4294967296
bluestore_csum = false
bluestore_csum_type = none
bluestore_bluefs_buffered_io = false
bluestore_max_ops = 30000
bluestore_max_bytes = 629145600
bluestore_buffer_cache_size = 104857600
bluestore_block_wal_size = 0
# use directory= option from fio job file
osd data = ${fio_dir}
# log inside fio_dir
log file = ${fio_dir}/log
####################################
#FIO jobs
#################
# Runs a 4k random write test against the ceph BlueStore.
[global]
ioengine=/usr/local/lib/libfio_ceph_objectstore.so # must be found in your LD_LIBRARY_PATH
conf=ceph-bluestore-somnath.conf # must point to a valid ceph configuration file directory=./fio-bluestore # directory for osd_data
rw=write
iodepth=16
size=256m
[bluestore]
nr_files=63
bs=4k # or 64k
numjobs=32
#############
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
PLEASE NOTE: The information contained in this electronic mail message is intended only for the use of the designated recipient(s) named above. If the reader of this message is not the intended recipient, you are hereby notified that you have received this message in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify the sender by telephone or e-mail (as shown above) immediately and destroy any and all copies of this message in your possession (whether hard copies or electronically stored copies).
N r y b X ǧv ^ ){.n + z ]z {ay ʇڙ ,j f h z w j:+v w j m zZ+ ݢj" ! i
��칻 �&�~�&���+-��ݶ��w��˛���m� �^��b��^n�r���z���h����&�� �G���h�(�階�ݢj"���m�����z�ޖ���f���h���~�m�
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
