"Connection timed out after 2000ms"

[stevage]

I am consistently getting message when attempting to upload a largeish (50MB) tileset. It always times out somewhere between 50 and 80 seconds after starting the upload:

4427 tiles @ 60/s, 21% complete [73s]
Connection timed out after 2000ms

Passing --timeout X doesn't seem to make any difference. (I suspect --timeout doesn't apply to the upload, but to something else).

Any ideas? Maybe it's something like after so many connections it starts taking a while to create new ones, then this 2 second cutoff kicks in?

[stevage]

Hmm, the source is fairly easy to find. In @mapbox/tilelive-s3:

        source.client = uri.client || new AWS.S3({
            s3ForcePathStyle: !!process.env.AWS_S3_ENDPOINT,
            region: source.region,
            endpoint: process.env.AWS_S3_ENDPOINT,
            maxRetries: 4,
            httpOptions: {
                timeout: 2000,
                agent: defaultAgent
            }
        });

2 seconds seems like a pretty aggressive timeout. I guess the issue now is to somehow make that configurable?

[stevage]

Huh. I have now discovered this was addressed here and it actually is configurable.

Solution: add ?timeout=10000 onto the end of the S3 URL.