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

Re: New (1.5) feature questions -- things we need to address before a release can happen

From: Justin Erenkrantz <justin_at_erenkrantz.com>
Date: 2007-10-24 17:39:16 CEST

On Oct 22, 2007 8:14 PM, David Summers <david@summersoft.fay.ar.us> wrote:
> When a large commit happens to the slave server (re-directed to the master
> via web-dav proxy) then sometimes for a long time (1.5 hours this last
> time) the user got errors on his client (I can get the exact error if
> people are interested) until the slave synced up with the master
> repository.

Hmm - it sounds like the svnsync isn't executing. Is this the case?
svnsync *should* be relatively fast - especially if the link between
slave<->master is fast enough.

But, I don't think this is a solvable problem - Karl's solution would
require a lot more intelligence in the proxy than there is now. You
just have to rely upon the synchronization happening fast enough. --

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Oct 24 17:39:40 2007

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.