[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Can I have mirrored subversion servers?

From: John Waycott <javajohn_at_cox.net>
Date: 2007-03-15 16:00:51 CET

Erik Huelsmann wrote:
> On 3/14/07, Duncan Murdoch <murdoch@stats.uwo.ca> wrote:
>> On 3/14/2007 8:21 AM, Edward Harvey wrote:
>> >> -----Original Message-----
>> >> From: Jared Hardy [mailto:jaredhardy@gmail.com]
>> >> Sent: Tuesday, March 13, 2007 9:42 PM
>> >> To: users@subversion.tigris.org
>> >> Cc: Edward Harvey
>> >> Subject: Re: Can I have mirrored subversion servers?
>> >>
>> >> The reason is: while replication/mirror solutions will
>> >> certainly speed up updates (or any read-only operation),
>> >> commits (write operations) should propagate to all repository
>> >> servers before they are considered "complete", no matter what
>> >> solution you choose.
>> >
>> > Well, I think that's just a matter of implementation. It is entirely
>> > possible, if a system were so designed, for the LAN repository to
>> accept
>> > a commit request from the client, and quickly reserve whatever it
>> needs
>> > to reserve on all the WAN repositories before returning success.
>> And if the LAN repository suffers a catastrophic failure (or a backhoe
>> takes out their WAN connection) before the commit really finishes, the
>> WAN repositories will be left waiting indefinitely, unable to process
>> updates or commit, while the local user may think everything is fine.
>> I don't know the details of what Eric hinted at for 1.5, but I hope that
>> it sticks with the model of a single master repository where commits
>> must succeed before a commit request returns.
> See
> http://svn.collab.net/repos/svn/trunk/notes/webdav-proxy
> for more information.
> bye,
> Erik.
We have development offices scattered throughout the world. We find that
the initial checkout takes the most time going to a central server.
Updates and commits are seldom a problem, thanks to Subversion's ability
to send/receive the deltas.

The workaround we use currently is to keep working copies of the project
trunks checked out to a local machines. This is a solution that Ryan
Schmidt mentioned a while ago, and it works very well for us. When a
developer wants to checkout a project, they just make a copy of the
locally checked-out working copy, then do an update or switch. The local
copies are updated about once a week or more to keep them current.

One big advantage for us is that it doesn't require remote SVN servers.
That translates to less administrative overhead. Any old desktop machine
will work fine for housing the local copies.

This doesn't solve the backhoe severing the WAN connection, but that is
seldom a problem for us since we have redundancy built into the network.

-- John

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Mar 15 16:01:28 2007

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.