1) Do not differentiate all-flash and hybrid(ssd+hdd) deployments since
they both bound to SSD drive backing DB volume.
2) Drop osd_delete_sleep_hybrid from 2s to 1s
3) Raise osd_delete_sleep_ssd to 1s since 0 is a way too low - having
it that low tend to cause a significant negative imact on OSD's regular
operation.
Signed-off-by: Igor Fedotov <ifedotov@suse.com>
.set_description("Time in seconds to sleep before next removal transaction for HDDs"),
Option("osd_delete_sleep_ssd", Option::TYPE_FLOAT, Option::LEVEL_ADVANCED)
- .set_default(0)
+ .set_default(1)
.set_description("Time in seconds to sleep before next removal transaction for SSDs"),
Option("osd_delete_sleep_hybrid", Option::TYPE_FLOAT, Option::LEVEL_ADVANCED)
- .set_default(2)
+ .set_default(1)
.set_description("Time in seconds to sleep before next removal transaction when data is on HDD and journal is on SSD"),
Option("osd_failsafe_full_ratio", Option::TYPE_FLOAT, Option::LEVEL_ADVANCED)