From: Fabrizio Cuseo <f.cuseo@panservice.it>
To: PVE User List <pve-user@pve.proxmox.com>
Subject: [PVE-User] Erasure coded pool and "rbd sparsify" - laggy pgs
Date: Mon, 2 Oct 2023 12:38:55 +0000 (UTC) [thread overview]
Message-ID: <1433103235.581941.1696250335102.JavaMail.zimbra@zimbra.panservice.it> (raw)
In-Reply-To: <313d9a10-46ab-6fba-49c7-4d5a82a83ba6@coppint.com>
Hello.
I am trying for the first time to setup an erasure coded pool with PVE 8.0
Cluster is 6 hosts, 24 OSD each one (12 ssd + 12 sas), 4x10Gbit.
One pool is replica 3 for ssd class drives (2048 PGs).
Another pool is replica 3 for hdd class drives (with 0.45 target ratio and 1024 PGs)
The last one, is an EC pool (4+2) sharing the same hdd class drives (with 0.5 target ratio, and 256 PGs).
Of course, pveceph creates the ec metadata pool, with replica 3, hdd class drives, 0.05 target ratio and 32 PGs.
If I move a drive from another storage to EC pool, i loose the sparse setting, so I need to "rbd sparsify" the rbd file.
But, when I do it on an EC pool, i can see ceph-osd processes using 100% cpu, and see on ceph mgr log, PGs in "active + laggy" state.
No any problem when I use the vm with drive image in erasure coded pool (but I think because is less IO intensive than a "sparsify").
Someone had the same problem or use EC pool for virtual machines ? I would like to have some "slow volumes" for archiving only purpose, but i am afraid that all the cluster could be impacted.
Regards, Fabrizio
next parent reply other threads:[~2023-10-02 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8931df75-0813-3aac-0481-f51afd328f6c@coppint.com>
[not found] ` <359756348.305396.1557210415135.JavaMail.zimbra@odiso.com>
[not found] ` <313d9a10-46ab-6fba-49c7-4d5a82a83ba6@coppint.com>
2023-10-02 12:38 ` Fabrizio Cuseo [this message]
2023-10-02 17:03 Fabrizio Cuseo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1433103235.581941.1696250335102.JavaMail.zimbra@zimbra.panservice.it \
--to=f.cuseo@panservice.it \
--cc=pve-user@pve.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox