[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

is hot-backup.py running in background from post-commit hooks safe?

From: Michael Kefeder <ml_at_weird-birds.org>
Date: 2003-07-13 20:57:37 CEST


Recently some of my subversion users complained about their subversion
client timing out when they commit, and i figured it was the post-commit
hook that introduced a too long delay before it finished. All the
post-commit hook does is runnning hot-backup.py and for some repositories
it's sending out commit-emails. What i did now was changing hot-backup.py
to run in background, then the clients don't timeout on commit.

Because one backup takes about 1 minute to complete it is very likely that
the same user commits a second time within that period of time or that
another user does a commit while a backup is running. I talked on your irc
channel about that and it seems that hot-backup.py does basic synchronizing
but it's not fully safe. A quick test where i did 4 parallel commits within
a few seconds was working ok for me (although it took 5 minutes for the
hot-backup.py instances to finish) - but still i'd like to know if it is
safe what i'm doing or not. Maybe there's a different way to do backups -
I'm open for everything. I guess fixing hot-backup.py to do fully
concurrent backups is a very hard task and may even be unnecessary
because... well, i don't know - enlighten me! ;)


p.s.: i'm not on the list, please include me on CC when answering.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Jul 13 21:03:13 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.