On 23 Jul 2013, at 17:16, Gregory Farnum wrote: >> And without wanting to sound daft having missed a salient configuration >> detail, but there's no way to release when it's written the primary? > > Definitely not. Ceph's consistency guarantees and recovery mechanisms > are all built on top of all the replicas having a consistent copy and > that breaks if you do primary-only acks. Maybe in the future something > like this will happen, but it's all very blue-sky right now. Saying that, another possibility is a persistent writeback cache on the client (either in qemu or in librbd), the former being something I'm toying with. Being persistent it can complete flush/fua type operations before they are actually written to ceph. It wasn't intended for this use case but it might be interesting. -- Alex Bligh _______________________________________________ ceph-users mailing list ceph-users@xxxxxxxxxxxxxx http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com