[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: Karl Fogel <kfogel_at_red-bean.com>
Date: 2007-10-23 08:08:45 CEST

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?


> 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.

> The other problem I've had with master/slave web-dav proxy mirroring
> is that it *should* still be able to read the slave even when the
> master is unreachable, but this turns out not to be the case. I had a
> discussion at
> http://svn.haxx.se/dev/archive-2007-03/0823.shtml and I sent a tcpdump
> but never got a reply.
> Should I enter this as an issue as well? This is only a problem when
> the master server is down (thankfully rare) but I'm also wondering if
> extra traffic is being sent to the master because of this?

Huh, yeah, that sounds like a separate bug, but still a bug.

Thanks for not forgetting about these issues!

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 23 08:09:16 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.