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

Re: svn clustering - sharing a mounted repository?

From: Ryan Schmidt <subversion-2007b_at_ryandesign.com>
Date: 2007-10-27 05:00:57 CEST

On Oct 26, 2007, at 11:59, Blair Zajac wrote:

> Ryan Schmidt wrote:
>> On Oct 25, 2007, at 10:13, t-man wrote:
>>> I am curious to about the potential ill effects (if any) of
>>> having two
>>> servers working off the same repository.
>>>
>>> The scenario would be as follows:
>>>
>>> Server A and Server B, both with the same repository that resides
>>> on a
>>> SAN mounted via nfs and the SAN being handled by GFS from RedHat,
>>> with
>>> a load balancer sitting on top.
>>>
>>> Part of me says that GFS would handle potential issues with
>>> concurrent
>>> writes - but the other part of me is afraid of the some operations
>>> blitzing the repository...
>>>
>>> Am I off the mark completely, or does anyone have a similar setup
>>> working somewhere, and if so, have they noticed any issues with
>>> that?
>> I have not personally tried it. But there was previous discussion
>> about this on the list, and I was led to understand that a SAN
>> with a cluster filesystem, such as Apple's Xsan, would adequately
>> insulate the various repository servers from one another so that
>> they would not clobber the repositories served on the SAN. I am
>> not familiar with GFS so I don't know whether it's a cluster
>> filesystem or how it compares to Xsan.
>
> There is a company that had this setup and the two heads both
> decided that they owned the physical disk at the same time and
> ended up corrupting the filesystem. They had off-site backups and
> were able to make a new filesystem and restore from the backup.

They used Apple's Xsan? Or some other filesystem? Was it a cluster
filesystem?

> Also, svn doesn't consume a large amount of resources, so it
> doesn't need this complicated of a set up. A single box can easily
> serve the traffic, just make sure you do post-commit hot backups of
> each commit and save them in multiple locations.

It might not just be for performance. It might also be for
reliability. It's great to know that any one server in your farm can
go down and not impact your users.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sat Oct 27 05:03:52 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.