On Fri, Apr 3, 2026 at 2:31 PM Anthony D'Atri via ceph-users <
[email protected]> wrote:

>
> > we expanded the cluster to 12 nodes with 28 osds
>
> 2 or 3 OSDs per node? Are these like Raspberry Pis, or maybe converged
> (Proxmox?)
>
28 osds per node.

>
> > but we are still running on EC 3+2, since we started cluster with 6
> nodes.
>
> There are ways to fake failure domains (hosts, racks, etc) when you *know*
> that a cluster will be expanding, albeit with increased risk until it does.
>
We use host failure domain for now.


> > We would like to change it to EC 6+3 or even EC 8+3? Is this reasonable
> or will 8+3 take too much
> > CPU/network capacities?
>
> That depends on several things.
>
> * Are you looking to change the profile to get more usable capacity?
>
* Are you looking to change the profile to get more durability / sustain
> more failures?
>
Not necessarily, we would rather have a responsive rgw for example during
failures, so when there is backfill/recovery going on that rgw does not
stop responding. It happened a few times. e.g. slow/faulty disk from on
which reweight was just set, was the reason that rgw stopped responding,
since some queue filled up ... because ceph was unable to read from faulty
pgs or smth...

> * What is your hardware like?  CPU, drive size/model, network links
>

There is a mix of:
- Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz with 20Gb network bonds
- AMD EPYC 9254 24-Core Processor with 50Gb network bonds

with mostly old 6T Seagate ST6000NM0095 drives, but we are just in the
process rotating them.


> * What kind of data are you storing?  RBD volumes? CephFS? Big files? Tiny
> files?
>

RGW, S3 users, backup data, nextcloud storage or just storage for placing
files. Mostly tiny files, however backups with >100GB or even TB files can
be found also.

usage:   775 TiB used, 1.0 PiB / 1.8 PiB avail

* Which Ceph release are you running?
>
> Reef 18.2.8

Rok
_______________________________________________
ceph-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to