Hi Istvan,

the issue you're referring to has nothing about real high latency ops.

It's just a cosmetic issue caused by improper ordering of the events which resulted in negative delta between them and hence showing that delta as a huge positive value.

But this impacts operations dump only. Fixed in 17.2.8 and upcoming 18.2.5, see https://tracker.ceph.com/issues/61388


Moreover please see the duration of the shared operation:

            "duration": 0.035560873999999999,

It's 35ms which might be not super low for NVMe/SSD-based OSD but that's 
definitely not a HUGE latency anyway.

So that's not a really bad slow operation...
And once again - huge value in the event timestamp is just a cosmetic issue 
isn't worth much attention.


Thanks,
Igor

On 18/02/2025 10:28, Szabo, Istvan (Agoda) wrote:
Hi,

I haven't really see much about this kind of event in ceph KB:
"event": "header_read",
"time": "2025-02-18T14:20:00.610389+0700",
"duration": 4294967295.999999

However we have huge latencies caused by this operation:

             "description": "osd_repop(client.3694832962.0:140533664 26.561 
e748587/706771 26:86be7203:::.dir.9213182a-14ba-48ad-bde9-289a1c0c0de8.3654639937.1.43:head v 
748587'789007122, mlcod=748587'789007120)",
             "initiated_at": "2025-02-18T14:20:00.610390+0700",
             "age": 87.067761466999997,
             "duration": 0.035560873999999999,
             "type_data": {
                 "flag_point": "commit sent; apply or cleanup",
                 "events": [
                     {
                         "event": "initiated",
                         "time": "2025-02-18T14:20:00.610390+0700",
                         "duration": 0
                     },
                     {
                         "event": "throttled",
                         "time": "2025-02-18T14:20:00.610390+0700",
                         "duration": 0
                     },
                     {
                         "event": "header_read",
                         "time": "2025-02-18T14:20:00.610389+0700",
                         "duration": 4294967295.999999
                     },
                     {
                         "event": "all_read",
                         "time": "2025-02-18T14:20:00.610402+0700",
                         "duration": 1.3264e-05
                     },
                     {
                         "event": "dispatched",
                         "time": "2025-02-18T14:20:00.610405+0700",
                         "duration": 2.3549999999999999e-06
                     },
                     {
                         "event": "queued_for_pg",
                         "time": "2025-02-18T14:20:00.610409+0700",
                         "duration": 3.8770000000000003e-06
                     },
                     {
                         "event": "reached_pg",
                         "time": "2025-02-18T14:20:00.610429+0700",
                         "duration": 2.0027e-05
                     },
                     {
                         "event": "started",
                         "time": "2025-02-18T14:20:00.610438+0700",
                         "duration": 9.8290000000000003e-06
                     },
                     {
                         "event": "commit_sent",
                         "time": "2025-02-18T14:20:00.645931+0700",
                         "duration": 0.035492616999999997
                     },
                     {
                         "event": "done",
                         "time": "2025-02-18T14:20:00.645951+0700",
                         "duration": 2.0007e-05
                     }


Is there a way to track it down what does this mean?

Thanks

________________________________
This message is confidential and is for the sole use of the intended 
recipient(s). It may also be privileged or otherwise protected by copyright or 
other legal rules. If you have received it by mistake please let us know by 
reply email and delete it from your system. It is prohibited to copy this 
message or disclose its content to anyone. Any confidentiality or privilege is 
not waived or lost by any mistaken delivery or unauthorized disclosure of the 
message. All messages sent to and from Agoda may be monitored to ensure 
compliance with company policies, to protect the company's interests and to 
remove potential malware. Electronic messages may be intercepted, amended, lost 
or deleted, or contain viruses.
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io
_______________________________________________
ceph-users mailing list -- ceph-users@ceph.io
To unsubscribe send an email to ceph-users-le...@ceph.io

Reply via email to