I can’t say anything about the pgremapper, but have you tried
increasing the crush weight gradually? Add new OSDs with crush initial
weight 0 and then increase it in small steps. I haven’t used that
approach for years, but maybe that can help here. Or are all OSDs
already up and in? Or you could reduce the max misplaced ratio to 1%
or even lower (default is 5%)?
Zitat von "Szabo, Istvan (Agoda)" <Istvan.Szabo@xxxxxxxxx>:
Forgot to paste, somehow I want to reduce this recovery operation:
recovery: 0 B/s, 941.90k keys/s, 188 objects/s
To 2-300Keys/sec
________________________________
From: Szabo, Istvan (Agoda) <Istvan.Szabo@xxxxxxxxx>
Sent: Friday, September 6, 2024 11:18 PM
To: Ceph Users <ceph-users@xxxxxxx>
Subject: Somehow throotle recovery even further than
basic options?
Hi,
4 years ago we've created our cluster with all disks 4osds (ssds and
nvme disks) on octopus.
The 15TB SSDs still working properly with 4 osds but the small 1.8T
nvmes with the index pool not.
Each new nvme osd adding to the existing nodes generates slow ops
with scrub off, recovery_op_priority 1, backfill and recovery 1-1.
I even turned off all index pool heavy sync mechanism but the read
latency still high which means recovery op pushes it even higher.
I'm trying to somehow add resource to the cluster to spread the 2048
index pool pg (in replica 3 means 6144pg index pool) but can't make
it more gentle.
The balancer is working in upmap with max deviation 1.
Have this script from digitalocean
https://github.com/digitalocean/pgremapper, is there anybody tried
it before how is it or could this help actually?
Thank you the ideas.
________________________________
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@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
_______________________________________________
ceph-users mailing list -- ceph-users@xxxxxxx
To unsubscribe send an email to ceph-users-leave@xxxxxxx
