Re: #739: Ensuring ACID in Subversion (aka watcher procecesses are fun)

Philip Martin <philip@codematters.co.uk> writes:

> > Alternative suggestions that do solve the problem are certainly
> > welcomed.
>
> It depends on how you define "completely and utterly robust" :-)
>
> Having all the clients receive SVN_ERR_REPOS_RECOVER and print
> "repository /foo/bar/repo requires recovery" and relying on the
> repository administrator running db_recover would do for me.

Having experimented a bit, it appears the clients just hang when there
is a repository problem. At least that's what happens at present. So
it may be difficult to generate an error. That doesn't really affect
my view of the solution, I still think manual intervention is the best
solution. It may be that a hanging client is what alerts the user,
rather than an explicit error message.

> At present, ra_local never loses data once it has been committed, it
> is "completely and utterly robust". All I want is to minimise the
> circumstances that cause SVN_ERR_REPOS_RECOVER. But when it does
> occur I am happy with manual intervention.

-- 
Philip Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org