In the thread "Re: <help>Database is Wedged for the 6th time.
Diagnostics or Prozac, anyone?" Peter Kahn wrote on 07.03.2005 at
17:40:
> I know that prior to going to 1.1.1 and svnserve we had one crash and
> that was due to a restart of the web server in the midst of a
> transaction.
We haven't had any problems with Subversion in the three weeks we've
been using it, but I wanted to make sure we're not setting ourselves up
for problems with the way we're using it.
We serve through an Apache 2 server that's also used for many other
things, and it happens probably at least weekly that some configuration
needs to be changed, which then means Apache has to be restarted. This
is done at times when people could certainly be committing to the
repository. As long as we always do a graceful restart, it seems to me
that it should not be possible for this to cause any problems for
Subversion. Do I see that correctly? What Subversion problems could be
caused by doing a normal non-graceful Apache restart? Would an ongoing
transaction simply be aborted, or do we risk repository corruption?
We're using Subversion 1.1.2 on Gentoo Linux with a single FSFS
repository. Client access is exclusively through Apache -- no svnserve
or direct file:/// access (although we do have a post-commit hook which
does various things with svn and svnlook with direct file:/// URLs).
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 8 13:27:16 2005