Just curious, can decreasing rocksdb_cf_compact_on_deletion_trigger 16384 > 4096 hurt performance of HDD OSDs in any way? I have no growing latency on HDD OSD, where data is stored, but it would be easier to set it to [osd] section without cherry picking only SSD/NVME OSDs, but for all at once.
I think that depends on your workload, but I'm not certain. If you don't override the OSD classes, you should be able to do something like "ceph config set osd/class:ssd rocksdb_cf_compact_on_deletion_trigger 4096". Josh On Fri, Jan 26, 2024 at 10:27 AM Roman Pashin <romanpashin28@gmail.com> wrote:
Unfortunately they cannot. You'll want to set them in centralized conf and then restart OSDs for them to take effect.
Got it. Thank you Josh! WIll put it to config of affected OSDs and restart them.
Just curious, can decreasing rocksdb_cf_compact_on_deletion_trigger 16384 > 4096 hurt performance of HDD OSDs in any way? I have no growing latency on HDD OSD, where data is stored, but it would be easier to set it to [osd] section without cherry picking only SSD/NVME OSDs, but for all at once.
-- Thank you, Roman _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io