Thanks Hyrum,
Thats a very interesting way of looking at this problem. It does make sense
that multiple commit processes coming from the same machine really wouldnt
be that different from the question I was asking. I guess from here I'll
have to do some testing somehow, with nfs in the mix and see if I can
purposly corrupt data by running many commit requests from two separate
apache nodes. But if what your saying is right, it sounds like i shouldnt
have much in the way of problems.
Thanks again!
B
On Mon, May 10, 2010 at 5:03 AM, Hyrum K. Wright <
hyrum_wright_at_mail.utexas.edu> wrote:
>
>
> On Fri, May 7, 2010 at 8:08 PM, BD <ccice05_at_gmail.com> wrote:
>
>>
>> So the question remains, taking physical restraints out of the question,
>> is there anyone out there who knows about managing the risks assocciated
>> with having two or more apache/svn nodes accessing repos that are stored on
>> a shared NFS storage system, with the SVN DBs using FSFS.
>
>
> I can't comment on your specific situation, but Subversion repositories are
> designed to be accessed by multiple concurrent processes, even if these
> processes are located on separate hosts. When using a single instances
> of Apache, for example, multiple requests can often spawn multiple processes
> which all interact (correctly) with the Subversion repository. In addition,
> the write-serialization window is relatively small, and writers do not block
> readers, so even during long-running parallel commits, read operations will
> still work as expected.
>
> Throwing NFS in the mix here may complicate things a bit, but probably not
> by much.
>
> -Hyrum
>
Received on 2010-05-10 16:53:11 CEST