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

Re: What happens if the repos is accessed during upgrade?

From: Mark Phippard <markphip_at_gmail.com>
Date: Tue, 27 May 2008 13:17:24 -0400

On Tue, May 27, 2008 at 12:28 PM, Dave Lawrence
<dlawrence_at_ad-holdings.co.uk> wrote:
> If when svn 1.5 finally arrives I do
>
> svnadmin upgrade repos
>
> 1) How long will it take (rough guess) on a 2GB repos with about 150000
> revisions. Are we talking minutes here or hours?

Seconds. It essentially just bumps an internal format number. See
the release notes for some details:

http://subversion.tigris.org/svn_1.5_releasenotes.html#repos-upgrades

> 2) What happens if someone tries to access the repository during that
> process?
>
> We use Apache on Linux

I believe it will lock the repository in the same way a commit would.

If you are using fsfs repositories you might ultimately want to
dump/load the repository to completely upgrade. This would get you
the new "sharded" repository format and a more efficient
node-origins-index cache.

One way to potentially do an upgrade is to use svnsync. You can
create a new 1.5 repository and use the 1.5 version of svnsync to
populate it while the current repository stays live. When the process
ends, you can just swap the repositories when you have a convenient
window.

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-05-27 19:17:48 CEST

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

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