On 10.08.2012 10:10, Johan Corveleyn wrote:
> 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?
I suppose anything that can make changes to the repository -- commit and
revprop change? -- should, if possible, detect the freeze and
immediately return an appropriate error. That's better than waiting
indefinitely and, worst-case, getting a client-side connection timeout.
-- Brane
--
Certified & Supported Apache Subversion Downloads:
http://www.wandisco.com/subversion/download
Received on 2012-08-10 10:19:57 CEST