svnsync fails to replicate large revision
From: Colin Foster <colin.Foster_at_in-advantage.com>
Date: Fri, 13 Jul 2018 20:01:13 +0000
Hello,
I'm not sure if this is a "bug", a "configuration issue", or simply a network issue. I'm hoping it is just a configuration issue.
I'm creating an off-site replica of our SVN server. Our current server is running the latest CollabNet SVNEdge server. Subversion version 1.8.19-4419.51
There was a large commit that fails after an indeterminate amount of time - sometimes 45 minutes, sometime 4.5 hours. I've been tinkering with Timout and KeepAlive settings to no avail.
The error I continue to see when the failure happens is:
The initial requests are seen here:
[13/Jul/2018:09:45:46 -0700] gregc IA rev-proplist r18116 9
With the failure showing up as such (note the timestamp of the two messages):
[13/Jul/2018:11:20:01 -0700] jenkins IA get-dir / /trunk r44281 props 0
[13/Jul/2018:09:45:54 -0700] gregc IA replay / r18116 5799
Relevant settings:
I have had to remove "mod_deflate" from loading - I believe this was due to crashes when transferring files > 4GB.
The server seems to be syncing at about 500KBps (4Mbps). The file "db/revs/18/18116" is 441 MB on disk: FSFS V6, Repo format 5, Not packed.
This is supposedly the message the client is exiting with (garbled with the output of "time"?):
That is all the relevant information I can think of in this instance. Seemingly the client is terminating the "svnsync synchronize" request. Or is this something in the server settings that is causing this issue? Or could this be something else?
Thank you very much!
[143421_logo_final_25]
|
This is an archived mail posted to the Subversion Users mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.