I think it's well explained on the docs: https://docs.ceph.com/en/reef/rados/operations/health-checks/#bluestore-slow... The parameters that modify that are these 2, which the defaults are a bit aggressive in my opinion: bluestore_slow_ops_warn_lifetime -> Interval to check (default 1 day) bluestore_slow_ops_warn_threshold -> number slow ops in the interval to trigger alert ( default 1) This means that 1 single slow op will maintain the alert for 1 day. To update: ceph config set global bluestore_slow_ops_warn_lifetime 10 ceph config set global bluestore_slow_ops_warn_threshold 5 To clean the alert, you can also reset bluestore_slow_ops_lifetime to any value so will restart the evaluation of the alert. ----------------------------------------------------------------- Roberto VALVERDE CAMESELLE IT Storage And Data Management CERN, European Organization for Nuclear Research Esplanade des Particules 1, Geneve (Switzerland) ________________________________ From: Frédéric Nass <frederic.nass@univ-lorraine.fr> Sent: Wednesday, June 18, 2025 11:58 AM To: Michel Jouvin <michel.jouvin@ijclab.in2p3.fr> Cc: ceph-users <ceph-users@ceph.io> Subject: [ceph-users] Re: How to clear the "slow operations" warning? Hi, This one? $ ceph config help bluestore_slow_ops_warn_lifetime bluestore_slow_ops_warn_lifetime - Set the time period during which a BlueStore slow ops warning will be raised when the `bluestore_slow_ops_warn_threshold` is exceeded. This is not the same as `osd_op_complaint_time`, which is about RADOS ops at the OSD level. (uint, advanced) Default: 86400 Can update at runtime: true See also: [bluestore_slow_ops_warn_threshold,osd_op_complaint_time] Found it here [1] as not in the documentation yet. Cheers, Frédéric. [1] https://github.com/ceph/ceph/blob/f484edf976c350b2f4b42fe15e0498fb30cc449a/s... ----- Le 18 Juin 25, à 8:43, Michel Jouvin michel.jouvin@ijclab.in2p3.fr a écrit :
Hi Jan,
There is a parameter (I don't remember the name but it is in the documentation!) to define how long the warning must remain after the condition has been cleared. By default it is 24h.
Cheers,
Michel Sent from my mobile Le 18 juin 2025 08:36:23 Jan Kasprzak <kas@fi.muni.cz> a écrit :
Hello again,
I still have problem with occasional "slow operations in BlueStore" warning, which I don't know how to clear/acknowledge except restarting that OSD process (or doihg "ceph osd down/up" cycle).
When I previously asked about this several weeks ago, the underlying cause was HDD with SMART errors logged. I replaced that disk eventually, but now I am occasionally getting the same warning from different OSDs, which do not have any SMART errors or pending/reallocated sectors.
How can I see whether it was one-time problem and now it is OK, and how can I clear the warning manually or automatically after some time?
Thanks!
-Yenya
Anthony D'Atri wrote:
Hello, Ceph users,
TL;DR: how to clear/acknowledge the following warning from ceph -s?
health: HEALTH_WARN 1 OSD(s) experiencing slow operations in BlueStore
Details: This is caused by a bad sector on the physical HDD - the time of this warning is the same as the most recent error in the SMART log of that HDD.
If this is the case, the drive might warrant replacement.
A few grown defects are not entirely alarming, but if there are more than, say, 10 then I’d replace the drive.
Or if there are SATA downshifts or other errors.
# ceph health detail HEALTH_WARN 1 OSD(s) experiencing slow operations in BlueStore [WRN] BLUESTORE_SLOW_OP_ALERT: 1 OSD(s) experiencing slow operations in
BlueStore
osd.33 observed slow operation indications in BlueStore
When I restart osd.33 using "systemctl restart ceph-osd@33.service" on the OSD host, the warning disappears. But is there a "softer" way how to acknowledge this warning?
ceph osd down 33
does not touch the process, only the maps and peering, which often suffices.
Thanks!
-Yenya
-- | Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> | | https://www.fi.muni.cz/~kas/ GPG: 4096R/A45477D5 | We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise. --Larry Wall _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
-- | Jan "Yenya" Kasprzak <kas at {fi.muni.cz - work | yenya.net - private}> | | https://www.fi.muni.cz/~kas/ GPG: 4096R/A45477D5 | We all agree on the necessity of compromise. We just can't agree on when it's necessary to compromise. --Larry Wall _______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
_______________________________________________ ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io
ceph-users mailing list -- ceph-users@ceph.io To unsubscribe send an email to ceph-users-leave@ceph.io