RE: SVN 1.8 timeout fix
Date: Wed, 15 Oct 2014 11:20:32 +0000
When I say we upgraded from 1.7 to 1.8, we configured and deployed a new server running CollabNetSubversion-server-1.8.9-2-Win32 that replaced our 1.7 server. All clients uninstalled 1.7, reinstalled 1.8 and rebooted.
I just tried setting SVNAllowBulkUpdates to Prefer and I re-enabled KeepAlive setting MaxKeepAliveRequests to 1000. That also seems to work for us.
When I initially used the default skelta-mode, small checkouts and commits worked perfectly fine. Large checkouts or commits would begin normally but the file transfer rate would quickly drop to 0 and the operation would time out. Increasing MaxKeepAliveRequests to 1000 didn't help. When I disabled KeepAlive, it solved the problem. However, with KeepAlive disabled, I discovered we can't browse repositories from a web browser. Apparently, this is a know serf bug. http://grokbase.com/t/subversion/users/136n5tvzx1/tsvn-and-svn-1-8-0-cannot-digest-authenticate.
> We just upgraded from Subversion 1.7 to 1.8 and almost immediately
I assume you are referring to an upgrade of the client from 1.7 to 1.8.
One change in 1.8 is that serf is used to handle HTTP on the client-side rather than neon. The default client-side HTTP timeout when using neon is 60 minutes but when using serf it is 10 minutes. A client can change its default timeout by setting servers:global:http-timeout.
If you upgraded the server to 1.8 then update/checkout will have switched to skelta-mode by default and I suppose configuring the client or server to use bulk-mode might solve the problem:
-- Philip Martin | Subversion Committer WANdisco // *Non-Stop Data*Received on 2014-10-15 13:21:03 CEST
This is an archived mail posted to the Subversion Users mailing list.