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

Re: Are multiple 'Location' tags with same 'SVNParentPath' safe?

From: Ryan Schmidt <subversion-2008b_at_ryandesign.com>
Date: Thu, 17 Apr 2008 13:48:05 -0500

On Apr 17, 2008, at 8:06 AM, James CE Johnson wrote:
> I have a Subversion repository that is protected by mod_auth_ldap:
>
> <Location /svn>
> DAV svn
> SVNParentPath /usr/local/svn/repositories
> SVNListParentPath on
> SVNAutoVersioning on
> AuthName "Enterprise Shared SCM Repository"
> AuthType Basic
> Require valid-user
> AuthLDAPUrl ldap://primaryLdapHost...
> AuthLDAPBindDN ...
> AuthLDAPBindPassword ...
> </Location>
>
> This works perfectly and we've been very happy with the results.
>
> However...
>
> I now have a different set of users who exist in a different LDAP
> repository. They will ultimately (in 6-9 months) join everyone else
> but,
> in the meantime, they need SVN access.
>
> So, the question is, will it be safe to create (in the same
> httpd.conf) a
> second <Location/> pointed to the same SVNParentPath?
>
> <Location /svnForOthers>
> DAV svn
> SVNParentPath /usr/local/svn/repositories
> SVNListParentPath on
> SVNAutoVersioning on
> AuthName "Enterprise Shared SCM Repository"
> AuthType Basic
> Require valid-user
> AuthLDAPUrl ldap://alternateLdapHost...
> AuthLDAPBindDN ...
> AuthLDAPBindPassword ...
> </Location>

I would guess that would be safe but wouldn't bet my own repository
on it at this point.

> If nobody has a definite answer, can anyone recommend test
> scenarios to
> prove or disprove that this will or will not result in repository
> corruption?

I'm not sure how you would test it.

> Related to this, and I will post it as a second query later, is it
> safe to
> have multiple Apache instances pointed to the same SVNParentPath
> (e.g. --
> clustering)?

It these multiple Apache instances are on multiple computers and
accessing a common repository on a storage-area network, then it will
be safe if the storage-area network uses a cluster filesystem. One
filesystem that has this is whatever Apple's Xsan uses.

An alternative to this would be to have just a single read/write
master repository, and then an arbitrary number read-only slaves
which use svnsync to synchronize with the master. You can even proxy
through the write requests so that someone can check out a working
copy from the read-only slave and when they commit the request will
be sent to the master. It's not entirely straightforward to set this
up, however.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-04-17 20:48:36 CEST

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