[ceph-users] Re: Assistance Needed with Ceph Cluster Slow Ops Issue
Hi Peter, try to set the cluster to nosnaptrim If this helps, you might need to upgrade to pacific, because you are hit by the pg dups bug. See: https://www.clyso.com/blog/how-to-identify-osds-affected-by-pg-dup-bug/ Mit freundlichen Grüßen - Boris Behrens > Am 06.12.2023 um 19:01 schrieb Peter : > > Dear all, > > > I am reaching out regarding an issue with our Ceph cluster that has been > recurring every six hours. Upon investigating the problem using the "ceph > daemon dump_historic_slow_ops" command, I observed that the issue appears to > be related to slow operations, specifically getting stuck at "Waiting for RW > Locks." The wait times often range from one to two seconds. > > Our cluster use SAS SSD disks from Samsung for the storage pool in question. > While these disks are of high quality and should provide sufficient speed, > the problem persists. The slow ops occurrence is consistent every six hours. > > I would greatly appreciate any insights or suggestions you may have to > address and resolve this issue. If there are specific optimizations or > configurations that could improve the situation, please advise. > > > below are some output: > > root@lasas003:~# ceph -v > ceph version 15.2.17 (542df8d06ef24dbddcf4994db16bcc4c89c9ec2d) octopus > (stable) > > > "events": [ > >{ >"event": "initiated", >"time": "2023-12-06T08:34:18.501644-0800", >"duration": 0 >}, >{ >"event": "throttled", >"time": "2023-12-06T08:34:18.501644-0800", >"duration": 3.067e-06 >}, >{ >"event": "header_read", >"time": "2023-12-06T08:34:18.501647-0800", >"duration": 3.5428e-06 >}, >{ >"event": "all_read", >"time": "2023-12-06T08:34:18.501650-0800", >"duration": 9.3397e-07 >}, >{ >"event": "dispatched", >"time": "2023-12-06T08:34:18.501651-0800", >"duration": 3.2832e-06 >}, >{ >"event": "queued_for_pg", >"time": "2023-12-06T08:34:18.501654-0800", >"duration": 1.381993999001 >}, >{ >"event": "reached_pg", >"time": "2023-12-06T08:34:19.883648-0800", >"duration": 5.7982e-06 >}, >{ >"event": "waiting for rw locks", >"time": "2023-12-06T08:34:19.883654-0800", >"duration": 4.248471164998 >}, >{ >"event": "reached_pg", >"time": "2023-12-06T08:34:24.132125-0800", >"duration": 1.0667e-05 >}, >{ >"event": "waiting for rw locks", >"time": "2023-12-06T08:34:24.132136-0800", >"duration": 2.159352784002 >}, >{ >"event": "reached_pg", >"time": "2023-12-06T08:34:26.291489-0800", >"duration": 3.292e-06 >}, >{ >"event": "waiting for rw locks", >"time": "2023-12-06T08:34:26.291492-0800", >"duration": 0.4391816470001 >}, >{ >"event": "reached_pg", >"time": "2023-12-06T08:34:26.730674-0800", >"duration": 5.1526e-06 >}, >{ >"event": "waiting for rw locks", >"time": "2023-12-06T08:34:26.730679-0800", >"duration": 1.053151686999 >}, >{ >"event": "reached_pg", >"time": "2023-12-06T08:34:27.783831-0800", >"duration": 5.1328e-06 >}, >{ >"event": "waiting for rw locks", >"time": "2023-12-06T08:34:27.783836-0800", >"duration": 1.232525088 >}, >{ >"event": "reached_pg", >"time": "2023-12-06T08:34:29.016361-0800",
[ceph-users] Re: Assistance Needed with Ceph Cluster Slow Ops Issue
Thank you for pointing this out. I did check my cluster by using the article given command, it over 17 million PG dups over each OSDs. May I know if the snaptrim activity takes place every six hours? If I disable the snaptrim, will it stop the slow ops temporarily before my performing version upgrade? If I want to upgrade my Ceph, it will take time to analysis the environment. Can I have work around quickly for delete OSD then create it again for zeroized the log times? or manually delete the OSD log? From: Boris Sent: Wednesday, December 6, 2023 10:13 To: Peter Cc: ceph-users@ceph.io Subject: Re: [ceph-users] Assistance Needed with Ceph Cluster Slow Ops Issue Hi Peter, try to set the cluster to nosnaptrim If this helps, you might need to upgrade to pacific, because you are hit by the pg dups bug. See: https://www.clyso.com/blog/how-to-identify-osds-affected-by-pg-dup-bug/ Mit freundlichen Grüßen - Boris Behrens Am 06.12.2023 um 19:01 schrieb Peter : Dear all, I am reaching out regarding an issue with our Ceph cluster that has been recurring every six hours. Upon investigating the problem using the "ceph daemon dump_historic_slow_ops" command, I observed that the issue appears to be related to slow operations, specifically getting stuck at "Waiting for RW Locks." The wait times often range from one to two seconds. Our cluster use SAS SSD disks from Samsung for the storage pool in question. While these disks are of high quality and should provide sufficient speed, the problem persists. The slow ops occurrence is consistent every six hours. I would greatly appreciate any insights or suggestions you may have to address and resolve this issue. If there are specific optimizations or configurations that could improve the situation, please advise. below are some output: root@lasas003:~# ceph -v ceph version 15.2.17 (542df8d06ef24dbddcf4994db16bcc4c89c9ec2d) octopus (stable) "events": [ { "event": "initiated", "time": "2023-12-06T08:34:18.501644-0800", "duration": 0 }, { "event": "throttled", "time": "2023-12-06T08:34:18.501644-0800", "duration": 3.067e-06 }, { "event": "header_read", "time": "2023-12-06T08:34:18.501647-0800", "duration": 3.5428e-06 }, { "event": "all_read", "time": "2023-12-06T08:34:18.501650-0800", "duration": 9.3397e-07 }, { "event": "dispatched", "time": "2023-12-06T08:34:18.501651-0800", "duration": 3.2832e-06 }, { "event": "queued_for_pg", "time": "2023-12-06T08:34:18.501654-0800", "duration": 1.381993999001 }, { "event": "reached_pg", "time": "2023-12-06T08:34:19.883648-0800", "duration": 5.7982e-06 }, { "event": "waiting for rw locks", "time": "2023-12-06T08:34:19.883654-0800", "duration": 4.248471164998 }, { "event": "reached_pg", "time": "2023-12-06T08:34:24.132125-0800", "duration": 1.0667e-05 }, { "event": "waiting for rw locks", "time": "2023-12-06T08:34:24.132136-0800", "duration": 2.159352784002 }, { "event": "reached_pg", "time": "2023-12-06T08:34:26.291489-0800", "duration": 3.292e-06 }, { "event": "waiting for rw locks", "time": "2023-12-06T08:34:26.291492-0800", "duration": 0.4391816470001 }, { "event": "reached_pg", "time": "2023-12-06T08:34:26.730674-0800", "duration": 5.1526e-06 }, { "event": "waiting for rw locks", "time": "2023-12-06T08:34:26.730679-0800", "duration": 1.053151686999 }, { "event": "reached_pg",
[ceph-users] Re: Assistance Needed with Ceph Cluster Slow Ops Issue
Snaptrim is the process of removing a snapshot and reclaiming diskspace after it got deleted. I don't know how the ceph internals work, but it helped for us. You can try to move the snaptrim into specific timeframes and limit it to one per osd. Also sleeping (3s worked for us) between the deletion helped to alleviate the pressure from the OSDs. Please check the documentation for the exact config parameters. I don't know if octopus got the tooling to remove the pg log dups. Check "ceph-objectstore-tool --help" if the --op parameter accepts trim-pg-log-dups croit made a blog post how to remove these dups: https://croit.io/blog/oom-killer-osds But be warned: Checking an 8TB Samsung SAS SSD with 300pgs (not trimming) took 4 hours. You can skip the listing and counting and just start the trim directly. But the OSD needs to be offline for it. What we did when we were hit with this issue: Stop snaptrim, update to pacific, do an offline rocksdb compression before the OSDs start after the upgrade, start the OSDs and hate our lives while they started, wait a week, slowly start the snaptrim and hope for the best. :-) Mit freundlichen Grüßen - Boris Behrens > Am 06.12.2023 um 20:17 schrieb Peter : > > > Thank you for pointing this out. I did check my cluster by using the article > given command, it over 17 million PG dups over each OSDs. > May I know if the snaptrim activity takes place every six hours? If I > disable the snaptrim, will it stop the slow ops temporarily before my > performing version upgrade? > If I want to upgrade my Ceph, it will take time to analysis the environment. > Can I have work around quickly for delete OSD then create it again for > zeroized the log times? or manually delete the OSD log? > > > > From: Boris > Sent: Wednesday, December 6, 2023 10:13 > To: Peter > Cc: ceph-users@ceph.io > Subject: Re: [ceph-users] Assistance Needed with Ceph Cluster Slow Ops Issue > > Hi Peter, > > try to set the cluster to nosnaptrim > > If this helps, you might need to upgrade to pacific, because you are hit by > the pg dups bug. > > See: https://www.clyso.com/blog/how-to-identify-osds-affected-by-pg-dup-bug/ > > > Mit freundlichen Grüßen > - Boris Behrens > >>> Am 06.12.2023 um 19:01 schrieb Peter : >>> >> Dear all, >> >> >> I am reaching out regarding an issue with our Ceph cluster that has been >> recurring every six hours. Upon investigating the problem using the "ceph >> daemon dump_historic_slow_ops" command, I observed that the issue appears to >> be related to slow operations, specifically getting stuck at "Waiting for RW >> Locks." The wait times often range from one to two seconds. >> >> Our cluster use SAS SSD disks from Samsung for the storage pool in question. >> While these disks are of high quality and should provide sufficient speed, >> the problem persists. The slow ops occurrence is consistent every six hours. >> >> I would greatly appreciate any insights or suggestions you may have to >> address and resolve this issue. If there are specific optimizations or >> configurations that could improve the situation, please advise. >> >> >> below are some output: >> >> root@lasas003:~# ceph -v >> ceph version 15.2.17 (542df8d06ef24dbddcf4994db16bcc4c89c9ec2d) octopus >> (stable) >> >> >> "events": [ >> >>{ >>"event": "initiated", >>"time": "2023-12-06T08:34:18.501644-0800", >>"duration": 0 >>}, >>{ >>"event": "throttled", >>"time": "2023-12-06T08:34:18.501644-0800", >>"duration": 3.067e-06 >>}, >>{ >>"event": "header_read", >>"time": "2023-12-06T08:34:18.501647-0800", >>"duration": 3.5428e-06 >>}, >>{ >>"event": "all_read", >>"time": "2023-12-06T08:34:18.501650-0800", >>"duration": 9.3397e-07 >>}, >>{ >>"event": "dispatched", >>"time": "2023-12-06T08:34:18.501651-0800", >>"duration": 3.2832e-06 >>}, >>{ >>"event": "queued_for_pg", >>"time": "2023-12-06T08:34:18.501654-0800", >>"duration": 1.381993999001 >>}, >>{ >>"event": "reached_pg", >>"time": "2023-12-06T08:34:19.883648-0800", >>"duration": 5.7982e-06 >>}, >>{ >>"event": "waiting for rw locks", >>