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

Bill Tutt wrote:

> If the watcher process detects an exiting registered process that hasn't
>
> deregistered then the datastore is now suspect. The watcher process
> must now cause all in process transactions to be aborted.
>
> This should probably be accomplished by using some asyncrhonous
> notification + timeout. If the timeout expires before the other
> remaining processes exit out, then the watcher process may kill the
> process explicitly.
>
> Once all of the registered processes have either exited with a useful
> failure message, or forcefully killed, then the watcher is allowed to
> recover the datastore.

how does the watcher process kill the other processes? are we going to
install it with the appropriate privs so that it can kill them? setuid
binaries give me the creeps...

also, would we have to have the watcher start up at system start? that
adds quite a bit of overhead to the process of creating a repository.
perhaps it would be possible to have the first svn process that tries to
access the repository start the watcher...

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Sep 19 18:40:54 2002