On Aug 18, 2009, at 06:22, Tobias Gierke wrote:
>> You can add read-only mirrors if you need more performance. If you
>> need everyone to be able to write too, then you can set up
>> write-through proxying on those mirrors.
> Good point. This would probably be the easier solution (though this
> whole 'svnadmin dump' stuff using a post-commit hook feels more like a
> hack, not like a feature).
That would be a hack. :) Perhaps you found outdated documentation.
Since Subversion 1.4, there is an officially supported way to keep a
read-only mirror: use the svnsync program. Though ideally you do call
it from the post-commit (and post-revprop-change) hook(s), since you
want it to synchronize as soon as any commit (or property change)
>> I have been told before that if you use a cluster filesystem like
>> Apple's Xsan, you can have multiple master servers pointing at the
>> same repositories and serving them simultaneously, which would help
>> eliminate your Subversion server as a single point of failure (and
>> instead make your NAS the single point of failure).
>> AFAIK NFS by itself is not a cluster filesystem and thus couldn't be
>> used in this manner.
> I can't see why you would need a cluster FS to do this. The main
> difference between a network FS (NFS,CIFS etc.) and a cluster FS is
> fact that a cluster FS doesn't use a central server to manage data
> access/locking. I think both solutions should work equally well
> (although performance most likely is quite different).
I don't have experience with these technologies myself, but I did
participate in prior discussions of the topic on this list, e.g.:
I don't know if that answers your question.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-08-18 13:39:27 CEST