Basically, it's an architectural choice: https://github.com/ceph/ceph/blob/master/doc/dev/osd_internals/erasure_coding/pgbackend.rst#client-writes If we wanted to support partial writes, we'd probably want to introduce a second EC pool type with different tradeoffs. Note, you can get slow partial writes on an EC pool by placing a replicated cache in front. -Sam On Fri, Jan 30, 2015 at 8:36 AM, Bassam Tabbara <bassamtabbara@xxxxxxxxxxx> wrote: > Hello, > > I realize that the EC Backend does not support all operations like partial writes, truncate, and others. I’d like to understand whether adding the missing operations is something that is architecturally possible, or if this is a limitation of the architecture / approach. Can someone shed some light on this? > > I realize that partial writes are going to be slow/inefficient on an EC backend compared to a replicated backend. > > Thanks! > Bassam-- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
