Maybe I should consider an upgrade of our Subversion server because the currently installed 1.1.x release seems to have problems handling the repository which has grown to 22 GB in the meantime. After some time of operation Apache processes grow and grow in size of memory and finally crash, leaving the Berkeley Database files in an inconsistent state. Maybe the most recent Subversion release does no longer have this problem.
Subscribe to:
Post Comments (Atom)
1 comment:
We upgraded ours for similar reasons, and have had a much smoother operation since. We used to have to recover the Berkeley backend weekly/fortnightly, but have not had to recover at all since switching to 1.3 and fsfs
http://aivipi.blogspot.com/2006/03/upgrading-subversion.html
--
Alan
Post a Comment