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

Re: Locking design (was Re: svn commit: r9885 - trunk/notes)

From: Branko Čibej <brane_at_xbc.nu>
Date: 2004-05-27 17:00:17 CEST

Mark Phippard wrote:

>By the way, I set the text to wrap at line 80 (it had a default of 70).
>What is the "proper" setting for that value to get the best compatability?
It's usually around 70.

>> This is not inconcievable at all. Modulo a few details regarding
>>synchronizing the repository configuration files and hooks, there's no
>>reason why this wouldn't work.
>But would you agree that if the locks were held in the repository layer,
>as opposed to the file system, that there would be a problem for this sort
>of scenario?
I would.

> It seems to me, that if the locks are in the repository
>layer, then they would not be visible to other instances of the Subversion
>server. I guess that perhaps those servers could all be configured to use
>a common filesystem to store the information, but that could lead to other
Yes. Note that unlike, say, hooks or svnserve configuration, which don't
have to be strictly in sync between different repos instances, the locks
table has to be. Incidentally, so does the mod_dav_svn activity database.

We're drifting a bit far afield now. Bottom line is that a lock table
outside the filesystem would make this kind of load balancing much
harder to do, or put in more bottlenecks.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu May 27 17:01:53 2004

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.