[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: SVN access became slow

From: Stefan Sperling <stsp_at_elego.de>
Date: Thu, 7 Jun 2018 10:43:38 +0200

On Thu, Jun 07, 2018 at 09:27:46AM +0200, Johannes van der Vegt wrote:
> Ok, I have the two instances running simultaneously now, and everything
> seems to be working. I trust your advice, backed by Daniel Shahaf, that this
> is a normal and proper situation.
>
> About the slow 1.10.0 client experience I had: trying IPv6 first and then
> falling back to IPv4 is normal, you told me, correct?

This depends on the choices taken by implementors of the
operating system's DNS resolver. It has nothing to do
with either SVN or APR (unless APR's DNS API wrappers
change the results returned from the system for some
reason, but I'd doubt it was doing that).

> And (Tortoise)SVN 1.9.7 went straight to IPv4 because of APR 1.5.2? Does APR
> 1.5.2 not support (or not default to) IPv6?

I don't know, and I don't have time to find out.
You could ask this question to the APR project: https://apr.apache.org

> Then a lot of users must have ran into this issue, right? Namely: Every user
> running an APR 1.5 SVN server, and a (Tortoise)SVN 1.10.0 client.

Most servers use Apache HTTPD which supports dual-stack operation.
This problem is specific to server deployments using the svn://
repository access method on IPv6-enabled servers.

> Well, my issue is solved now. Thanks for the support!!!

Glad we could help. You're welcome :)
Received on 2018-06-07 10:44:13 CEST

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.