[
https://issues.apache.org/jira/browse/SVN-4201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Zhakov updated SVN-4201:
-----------------------------
Affects Version/s: (was: 1.7.x)
1.7.0
> replay ordering/data out of sync on broken connection
> -----------------------------------------------------
>
> Key: SVN-4201
> URL: https://issues.apache.org/jira/browse/SVN-4201
> Project: Subversion
> Issue Type: Bug
> Components: libsvn_ra_serf
> Affects Versions: 1.7.0
> Reporter: Bert Huijben
>
> {noformat:nopanel=true}
> Reported privately:
> (and noted on irc a few weeks ago)
> When using svnsync to migrate a repository, sometimes a connection might
> break
> due to network problems.
> The new in 1.7 code then tries to send the same request and continue where
> the
> connection broke down.
> This user got two separate issues, that probably have the same root cause:
> * The assertion that the content-length had shrunk triggered.
> * The revision number check failed as the target repository has a revision to
> much, while only a single svnsync process used the repository.
> Eventually the sync succeeded after a few attempts (and switching to the much
> slower ra_neon)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
