Hello,
What IO size are you testing, Bluestore will only defer writes under
32kb is size by default. Unless you are writing sequentially,
only limited amount of buffering via SSD is going to help, you will
eventually hit the limits of the disk. Could you share some more
details as I'm intere
On Monday, February 18, 2019 16:44 CET, David Turner
wrote:
> Has anyone else come across this issue before? Our current theory is that
> Bluestore is accessing the disk in a way that is triggering a bug in the
> older firmware version that isn't triggered by more traditional
> filesystems. We
Numbers are easy to calculate from RocksDB parameters, however I also
don't understand why it's 3 -> 30 -> 300...
Default memtables are 256 MB, there are 4 of them, so L0 should be 1 GB,
L1 should be 10 GB, and L2 should be 100 GB?
These sizes are roughly 3GB,30GB,300GB. Anything in-between
Jewel is really limited on the settings you can tweak for backfilling [1].
Luminous and Mimic have a few more knobs. An option you can do, though, is
to use osd_crush_initial_weight found [2] here. With this setting you set
your initial crush weight for new osds to 0.0 and gradually increase them
t
Hello everybody,
I try to improve the backfilling proccess without impact my client I/O,
that is a painfull thing when i putted a new osd in my environment.
I look some options like osd backfill scan max , Can I improve the
performance if I reduce this ?
Someome recommend parameter to study in
