> From: Brandon Ehle [mailto:firstname.lastname@example.org]
> >>>We'd like to switch to it as we are having tons of problems with
> >>>apache deadlocking and leaking semaphores.
> >Considering that ra_svn is a newborn baby, hardly tested, and likely
> >full of bugs at the moment... I think you're making a pretty silly
> Granted, I don't want to make the switch but I'm sort of stuck up s***
> creek without a paddle. I want to track down the apache bugs and fix
> them, but in the meantime, the rest of my team needs the repository up
> and running. Unless you can suggest another way to get the repository
> to work for updates, checkouts, & commits; I need to find any way I
> to get the repository running before I get into any bug tracking.
> seems my only solution as mounting the repository over SAMBA probably
> isn't very safe.
> >On IRC, you kept describing about how httpd children were
> >constantly hanging and/or causing repository wedges. You stated that
> >this problem seemed to get worse as the repository grew bigger (to
> >and beyond). I think the better approach here is to work with Apache
> >and SVN developers, and figure out why you're seeing these problems.
> Yes, I've noticed some general reproduction recipes, but I need to
> a way to get our repository running again before I can attempt to
> down these issues.
I know somebody has mentioned it before. I'll mention it again. You need
to recover the database. The exact syntax to recover is either in the
mailing list archive or in the FAQ someplace.
The short term solution for SVN, and I'm not sure that ra_svn changes
this at all (I haven't read the code) is to add BDB lock timeouts. The
trouble being how long should the timeout be? I'm going to take a stab
and say 2min should definitely be more than long enough, or your
Subversion server is too overloaded in the first place.
After we do that if the children still hang then we'll start needing
more reproducible test cases.
Having said all of the above: You're using Subversion in production? Are
you nuts? We haven't released yet. ;)
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Wed Dec 4 15:06:14 2002