>"Bob Wilken" <email@example.com> writes:
> > It likely wouldn't bother me so much -- except I now have 50+
> > repositories hosted off a single apache instance taking the approach
> > of a repository per project. The probability of hosing another project
> > during a recovery of one is quite high so I need to run recover on
> > all... really not a pretty picture.
>Sorry, what do you mean by "The probability of hosing another project
>during a recovery of one is quite high so I need to run recover on
>all" ? Why does running recovery on one project hose a separate
>repository? What symptoms are you seeing?
>Or by "hosing", do you just mean that access is down because Apache is
Sorry, the concern would be that while taking Apache off-line to work
on it I am unable to control the access by other clients... implication
that if someone was in the middle of a transaction against another of
the hosted 50+ projects when I pull the rug out from them, well I'm
a bit concerned that I'll likely need to recover that project in addition
to the one that I set out to recover and since I have no way of really
predicting which projects are being accessed I figured I'd end up forcing
a recovery of all... and likely have several frustrated clients.
> > What OS is Subversion itself running off? Any tips on how it is
> > configured or how frequently you run recover with so many uncontrolled
> > clients accessing - how do you prevent them from locking up your
> > database?
>svn.collab.net is running RedHat Linux, I believe.
>We've just started having similar problems, actually, but were busy
>with meta-work last week and haven't had a chance to look into it yet.
>We suspect something is wonky about SVN's usage of Berkeley DB.
Perhaps it's not just my configuration then, which issue# is this being
Add photos to your e-mail with MSN 8. Get 2 months FREE*.
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Thu Aug 7 00:42:21 2003