6 Apr
2024
6 Apr
'24
5:51 p.m.
Hi,
Do slow ops impact data integrity => No
Can I generally ignore it => No :)
This means that some client transactions are blocked for 120 sec (that's a
lot).
This could be a lock on the client side (CephFS, essentially), an incident
on the infrastructure side (a disk about to fall, network instability,
etc.), ...
When this happens, you need to look at the blocked requests.
If you systematically see an osd ID, then look at dmesg and the SMART of
the disk.
This can also be an architectural problem (for example, high IOPS load with
osdmap on HDD, all multiplied by the erasure code)
*David*
Le ven. 5 avr. 2024 à 19:42, adam.ther <adam.ther(a)aol.com> a écrit :
Hello,
Do slow ops impact data integrity or can I generally ignore it? I'm
loading 3 hosts with a 10GB link and it saturating the disks or the OSDs.
2024-04-05T15:33:10.625922+0000 mon.CEPHADM-1 [WRN] Health check
update: 3 slow ops, oldest one blocked for 117 sec, daemons
[osd.0,osd.13,osd.14,osd.17,osd.3,osd.4,osd.9] have slow ops.
(SLOW_OPS)
2024-04-05T15:33:15.628271+0000 mon.CEPHADM-1 [WRN] Health check
update: 2 slow ops, oldest one blocked for 123 sec, daemons
[osd.0,osd.1,osd.14,osd.17,osd.3,osd.4,osd.9] have slow ops. (SLOW_OPS)
I guess more to the point, what the impact here?
Thanks,
Adam
_______________________________________________
ceph-users mailing list -- ceph-users(a)ceph.io
To unsubscribe send an email to ceph-users-leave(a)ceph.io