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

Re: svn_fs/svn_repo repository lock API

From: Johan Corveleyn <jcorvel_at_gmail.com>
Date: Fri, 10 Aug 2012 10:10:02 +0200

On Fri, Aug 10, 2012 at 1:09 AM, Philip Martin
<philip.martin_at_wandisco.com> wrote:
> Ben Reser <ben_at_reser.org> writes:
>
>> On Thu, Aug 9, 2012 at 12:51 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>>> What does a frozen repository actually look like for clients? I assume
>>> only write operations are affected. What happens to a commit or a
>>> propset or a revprop change?
>
> Anything that attempts to write will block either until the freeze is
> over or some timeout occurs depending on how the writer has been
> designed.
>
> For a live repository with commits going on the command
>
> freeze-program repository -c command
>
> causes attempts to take new write-locks to block, waits until existing
> write-locks are released, and then runs the command with the repository
> frozen. When the command finishes the freeze-program exits which
> unfreezes the repository thus allowing the blocked write-locks to
> proceed.

So, say for a standard 1.8 FSFS repository, is there a timeout for
commits? What's the timeout (is it configurable?)? How will the commit
fail when it reaches the timeout?

-- 
Johan
Received on 2012-08-10 10:11:06 CEST

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