You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Trent Fisher <tr...@oracle.com> on 2022/11/14 14:53:22 UTC
Re: [External] : Re: svnsync: E120106: ra_serf: The server sent a truncated HTTP response body.
I have seen this sort of thing, and I think the cause is that it is
taking SVN a long time to put together the transaction and, during that
time, no data is going through the HTTP pipe and the connection times
out. I am pretty sure the Apache setting to change here is "Timeout".
On 11/14/2022 8:58 AM, Daniel Sahlberg wrote:
> Den mån 14 nov. 2022 kl 13:31 skrev JITHIN K <ji...@gmail.com>:
>
> Hello Team,
>
> I use Subversion 1.13 in Ubuntu 20.04.5 LTS and sync a
> repository size of 300GB to a mirror server ( same version of SVN
> and OS ).
>
> I get the following warning svnsync: E120106: ra_serf: The server
> sent a truncated HTTP response body every time ( I had to take a
> dump of specific revisions and load it in the mirror server ).
> Did anyone face this problem while in sync? Is there any solution?
>
>
> Do you see any common pattern with the revisions causing trouble?
> Possibly if they are very large or contain a lot of files.
>
> This was mentioned once before on the list [1]. I don't see if the
> user found a way around it, but he mentions that the troublesome
> revisions were large imports.
>
> Kind regards,
> Daniel
>
> [1] https://lists.apache.org/thread/cmc872c221o0r5mvhk16lcjfnd4xwtl1
> <https://urldefense.com/v3/__https://lists.apache.org/thread/cmc872c221o0r5mvhk16lcjfnd4xwtl1__;!!ACWV5N9M2RV99hQ!PpXDqyCTr-nxClhPwoIkFaoBg7wK-DmrDGdyi4EEqASjo1oiOxKwlq2DHH9HDKIu2NeowK7326qMGkwRj02I40t-vMZd$>
>
I have seen this sort of thing, and I think the cause is that it is
taking SVN a long time to put together the transaction and, during that
time, no data is going through the HTTP pipe and Apache thinks the
connection is idle and kills it. I have seen this both with svn and
user checkins, in the latter case the checkin contains thousands of
changed files. I was able to see this in action by looking at what
files were changing within the (replica) repository itself and I could
see files in "transactions" (or was it "txn-protorevs"?) and I could see
them slowly growing as each change was written into them.
I am pretty sure the Apache setting to change here is "Timeout". There
may be other settings I am forgetting about, it has been some time since
I have seen this.
It is possible there may be some filesystem tuning which could speed up
the file writes, but I have no direct experience with that.