live-mirroring of repository

Dave S snidely.too at gmail.com
Wed May 6 00:16:37 UTC 2015


On Tue, May 5, 2015 at 5:03 PM, Gregory Szorc <gregory.szorc at gmail.com>
wrote:


> Multi master is hard. Period.
>

I'm thinking most small setups would use an active-passive arrangement,
where everybody tries to push to A, and only A tries to push to B.

B would only be used directly if A was down.

One weakness would be if A committed a push successfully, but went down
before passing it on to B.  That wouldn't be known until you get A back up,
I'm thinking.  But otherwise, B should be reasonably current.  I'd probably
use client shell scripts to emulate failover (make B active) if it was
necessary for this to be automatic.  Once A was back online, it might take
some administrator time to make sure the repos were in sync.

But Matt's links to the FB SQL stuff should lead to some good reading.

/dps


-- 
test signature -- please apply at front gate on Tuesdays only.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150505/64786ae0/attachment-0002.html>


More information about the Mercurial mailing list