With k=2 and m=1 you cannot do any maintenance with redundancy. Any fail requires immediate attention. Its a recipe for data loss. There have been lengthy discussions about why, in production, min_size>=k+1 is recommended and why min_size=k is not.
For any k, with m=1 you either have service outage on any maintenance event (min_size>=k+1), or risk data loss for fresh writes to non-redundant storage (min_size=k). ================= Frank Schilder AIT Risø Campus Bygning 109, rum S14 ________________________________________ From: Vitaliy Filippov <vita...@yourcmc.ru> Sent: 14 February 2020 00:10:03 To: Anthony Brandelli (abrandel); Martin Verges Cc: ceph-users@ceph.io Subject: [ceph-users] Re: EC Pools w/ RBD - IOPs > please do not even think about using an EC pool (k=2, m=1). See other > posts here, just don't. Why not? -- With best regards, Vitaliy Filippov _______________________________________________ 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
