On Wed, 24 Oct 2007, Justin Erenkrantz wrote:
> 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.
I have each commit start a svnsync from the master to the slave server.
> 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. --
> justin
>
The master is in Huntsville, AL, and the slave is in Lowell, AR, across
the Internet. Most of the time there is no problem at all but when the
the commit passes some magic number of bytes or seconds then the client
freaks out. The other day, I kept getting errors from the client for 1.5
hours after the (big) commit until the slave and master had synced up.
Sometimes we have to mess around with the client files to get it to stop
misbehaving (waving hands here, I don't recall all the things I've tried).
David Wayne Summers "Linux: Because reboots are for hardware upgrades!"
david_at_summersoft.fay.ar.us PGP Key: http://summersoft.fay.ar.us/~david/pgp.txt
PGP Key fingerprint = 0B44 B118 85CC F4EC 7021 1ED4 1516 5B78 E320 2001
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Thu Oct 25 03:12:00 2007