On Mon, 22 Oct 2007, Karl Fogel wrote:
> David Summers <david@summersoft.fay.ar.us> writes:
>> 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.
>>
>> This happens 100% of the time if the commit is beyond some magic
>> number of megabytes (or seconds, not sure which).
>>
>> Should I enter this as a problem in the issue tracker so we don't
>> forget about it?
>
> +1
Posted as issue # 2988.
>> Karl had some suggestions about a couple of different ways to fix it.
>>
>> Is this something that would be "easy" to do?
>
> I don't think so. The right fix is for the slave to proxy over to the
> master for reads as well, when a client requests a revision higher
> than the slave's current youngest.
>
> An alternative (for less load on the slave) is for the client to
> notice the particular error from the slave, and contact the master
> itself. But that might have working copy metadata implications.
>
> I don't think that...
>
>> It would be SUPER SWEET if this could be fixed for 1.5.0.
>
> ... solving this for 1.5.0 is realistic, though would love to be
> proven wrong of course.
>
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 Wed Oct 24 04:31:16 2007