>
>
>>>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
>decision.
>
>
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 can
to get the repository running before I get into any bug tracking. This
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 6GB
>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 find
a way to get our repository running again before I can attempt to track
down these issues.
>(IIRC, Gustavo Niemeyer is running a 5GB repository and *not* having
>these problems.)
>
>
5GB of what? 5GB of strings or 5GB of strings+log.* files?
We are currently running with a 3.2GB strings file and 5GB of log.* files.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Dec 4 14:49:11 2002