Hg server replication

[Wing Choi]

It does the reserve ahead when you push to the local replication
server.  The advantage is that the local push is faster and is
decoupled from the slower replay into primary sitting in another 
geo.  The repliation server in other locales then syncs from the
primary at their own accord; and the users from each locale can 
pull the new txn from the own local replication server.  It saves 
the multitudes of folks in other locales from having to all trying 
to pull from a distance server.

So, while mechanistically ab reductio, perhaps it's the same,
the end effect is we get local replication and not wasting an entire
bunch of people's time repeatedly.


thus spake Dustin Sallings on Wed, Nov 07, 2007 at 12:17:33AM -0800:
> 
> On Nov 6, 2007, at 20:34, Wing Choi wrote:
> 
> >I am using svk (with Pushmi) and that is sort of what it does now.
> >There isn't a lock server, it does a reserve ahead with the primary
> >(obviously, any other simultaneous push attempts that does not get
> >the reserve ahead will back off and that/those user(s) will have
> >to pull and merge b4 retrying the push) and then replay the
> >transaction over to the primary once the push from the local
> >client is complete.
> >
> >How can something similar be accomplished in Hg?
> 
> 
> 	Does it lock all of them before starting any?  If not, it sounds 
> 	like  the same thing that would happen if you just tried a regular push  
> against a server.
> 
> -- 
> Dustin Sallings
> 
> 
> 

-- 

Nothing is really work unless...
you'd rather be doing something else

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 477 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20071107/b15fb47b/attachment.pgp