Hmm, that's kind of risky. What if you good leg fails before the sync happens to the secondary leg? Replay cache may serve as a lifeline in such a scenario.
Thanks -Anoop ----- Original Message ----- From: "Ravishankar N" <ravishan...@redhat.com> To: "Anoop Nair" <ann...@redhat.com>, gluster-devel@gluster.org Sent: Wednesday, August 12, 2015 5:46:04 PM Subject: Re: [Gluster-devel] semi-sync replication On 08/12/2015 12:50 PM, Anoop Nair wrote: > Hi, > > Do we have plans to support "semi-synchronous" type replication in the > future? By semi-sync I mean writing to one leg the replica, securing the > write on a faster stable storage (capacitor backed SSD or NVRAM) and then > acknowledge the client. The write on other replica leg may happen at later > point in time. Not exactly in the way you describe, but there are plans to achieve "near-synchronous" replication wherein we wind the write to all replica legs, but acknowledge success as soon as we hear a success from one of the bricks (instead of waiting for responses from all bricks as we do today). -Ravi > > > Thanks > -Anoop > _______________________________________________ > Gluster-devel mailing list > Gluster-devel@gluster.org > http://www.gluster.org/mailman/listinfo/gluster-devel _______________________________________________ Gluster-devel mailing list Gluster-devel@gluster.org http://www.gluster.org/mailman/listinfo/gluster-devel
