Comparing Ceph, Linstor, Mayastor and Vitastor Storage Performance in Kubernetes

Re:Comparing Ceph, Linstor, Mayastor and Vitastor Storage Pe... by tlamponi on Saturday June 04, 2022 @05:07AM (#31618381)

Sure does, you can create a pool with that target/minimum replica just fine, there are some hosters that thought they were improving performance and data usage (which, well, is true), but ignored the impossibility of having any real redundancy at all; note that 2/2 is just fine though, but the pool will go read only if one failure domain goes down (compared to 3/2 where you can continue operating just fine in such a case).

IOW. 2/1 will never ever make sense, it's just crying for data loss, if you want to save on data usage, and if you also don't mind the (slightly) higher CPU load, you can use erasure coding instead:

https://pve.proxmox.com/pve-docs/chapter-pveceph.html#pve_ce... https://docs.ceph.com/en/latest/rados/operations/erasure-cod...

[ Parent | on HN ]

Re:Comparing Ceph, Linstor, Mayastor and Vitastor Storage Pe... by IcePic on Wednesday June 08, 2022 @06:21AM (#31665330)

It still doesn't mean it accepts the write as finished when only 1 PG has it. I agree on the risks on why 2/1 is stupid, just not that this also means writes finish faster with min_size < replication_factor.

[ Parent | on HN ]

Re:Comparing Ceph, Linstor, Mayastor and Vitastor Storage Pe... by tlamponi on Friday June 17, 2022 @01:18AM (#31774371)

It does though, it defines when to complete the write command to a client and when general any IO should be allowed on an object (both need #copies >= min-size), from the Quincy PG settings docs:

  > Sets the minimum number of written replicas for objects in the pool in order
  > to acknowledge an I/O operation to the client. If minimum is not met, Ceph
  > will not acknowledge the I/O to the client, which may result in data loss.
  > This setting ensures a minimum number of replicas when operating in degraded
  > mode.

[ Parent | on HN ]