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

Re: multiple svn front-ends, single SAN repo volume

From: Ryan Schmidt <subversion-2012a_at_ryandesign.com>
Date: Fri, 10 Feb 2012 16:20:02 -0600

On Feb 10, 2012, at 16:16, Stefan Sperling wrote:
> On Fri, Feb 10, 2012 at 04:09:45PM -0600, Ryan Schmidt wrote:
>> you could consider having any
>> number of read-only slave servers, which would each proxy their write
>> requests back to the single master server that Subversion supports.
>> This way read operations would be accelerated, while write operations
>> would be securely limited to just the single master. The slave servers
>> could keep individual copies of the repository(ies) synchronized with
>> the master using svnsync
> This is misleading. A write-through proxy setup does not eliminate
> write operations on slave servers.

Oh I see! That is not how I had envisioned it happening, so thank you for the clarification.

> While replicating commits, svnsync performs the exact same kinds of
> write operations against the slave servers that happen on the master
> repository when a client makes a commit.

So when using svnsync one should always use a separate and preferably local copy of the repository(ies) on each server, yes?
Received on 2012-02-10 23:20:59 CET

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.