You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Dave Lawrence <dl...@ad-holdings.co.uk> on 2008/05/27 16:28:53 UTC
What happens if the repos is accessed during upgrade?
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?
2) What happens if someone tries to access the repository during that
process?
We use Apache on Linux
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: What happens if the repos is accessed during upgrade?
Posted by Dave Lawrence <dl...@ad-holdings.co.uk>.
Dave Lawrence 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?
Whoops I meant about 15000 revisions.
> 2) What happens if someone tries to access the repository during that
> process?
>
> We use Apache on Linux
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: What happens if the repos is accessed during upgrade?
Posted by Andy Levy <an...@gmail.com>.
On Tue, May 27, 2008 at 12:28 PM, Dave Lawrence
<dl...@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?
>
> 2) What happens if someone tries to access the repository during that
> process?
>
> We use Apache on Linux
Why not take the repository offline (shut down Apache) while you're
performing the upgrade and remove all doubt about what will happen if
someone attempts to access it?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: What happens if the repos is accessed during upgrade?
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, May 27, 2008 at 3:38 PM, <km...@rockwellcollins.com> wrote:
> Does this get sharding as well? I'd really like to split up some
> db/revs directories of our larger repos that have 100k+ revisions.
It doesn't, but there is a Python script provided to "shard" a
repository. So yes, it can be done.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: What happens if the repos is accessed during upgrade?
Posted by km...@rockwellcollins.com.
"Mark Phippard" <ma...@gmail.com> wrote on 05/27/2008 02:23:58 PM:
> On Tue, May 27, 2008 at 3:18 PM, <km...@rockwellcollins.com> wrote:
>
> >> 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.
> >
> > Will this preserve any file locks from the old repository? I know
> > that a dump/load process doesn't. Is it feasible that a
> > script could help propagate locks?
>
> AFAIK, locks do not get synched via svnsync. I cannot answer the
> script question. I wonder of the locks folder (is that were they are
> stored in fsfs?) could just be moved/replaced in the svnsynced version
> when the process was concluded? The internal ID's change with 1.5, so
> if locks use those, then probably not.
I wasn't daring enough to try just copying and pasting the locks folder,
but it had crossed my mind.
> I'd say you'd probably just want to use svnadmin upgrade and build the
> node-index-origins index. The size/performance penalty of doing it
> this way is fairly small.
Does this get sharding as well? I'd really like to split up some
db/revs directories of our larger repos that have 100k+ revisions.
Kevin R.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: What happens if the repos is accessed during upgrade?
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, May 27, 2008 at 3:18 PM, <km...@rockwellcollins.com> wrote:
>> 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.
>
> Will this preserve any file locks from the old repository? I know
> that a dump/load process doesn't. Is it feasible that a
> script could help propagate locks?
AFAIK, locks do not get synched via svnsync. I cannot answer the
script question. I wonder of the locks folder (is that were they are
stored in fsfs?) could just be moved/replaced in the svnsynced version
when the process was concluded? The internal ID's change with 1.5, so
if locks use those, then probably not.
I'd say you'd probably just want to use svnadmin upgrade and build the
node-index-origins index. The size/performance penalty of doing it
this way is fairly small.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: What happens if the repos is accessed during upgrade?
Posted by km...@rockwellcollins.com.
"Mark Phippard" <ma...@gmail.com> wrote on 05/27/2008 12:17:24 PM:
> On Tue, May 27, 2008 at 12:28 PM, Dave Lawrence
> <dl...@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.
Will this preserve any file locks from the old repository? I know
that a dump/load process doesn't. Is it feasible that a
script could help propagate locks?
Kevin R.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: What happens if the repos is accessed during upgrade?
Posted by Mark Phippard <ma...@gmail.com>.
On Tue, May 27, 2008 at 12:28 PM, Dave Lawrence
<dl...@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@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org