Skip to content

Conversation

@thomas-riccardi
Copy link
Contributor

@thomas-riccardi thomas-riccardi commented Nov 14, 2019

Closes #77

In fact requests connect timeout is not just TCP connect, but
also includes sending the whole HTTP request, which can be much
longer than 3s for Network uploads.

Before the issue is fixed in requests we should not fail long
uploads: stop using advanced timeouts for now.

Also decreased FAST timeout from 10 to 8 so we are guaranteed to have
at least 3 tries with the 60s timeout on tasks GET loop.

@thomas-riccardi thomas-riccardi force-pushed the hotfix-77-network_upload_timeout branch from 7bbe5d6 to ff2dae7 Compare November 14, 2019 14:37
@thomas-riccardi thomas-riccardi added priority/high Issue to solve quickly READY labels Nov 14, 2019
FAST = (3.05, 10.)
MEDIUM = (3.05, 60.)
SLOW = (3.05, 600.)
FAST = 8.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't we want to put your explanations as code comment ?

In fact `requests` `connect` timeout is *not* just TCP connect, but
also includes sending the whole HTTP request, which can be much
longer than 3s for Network uploads.

Before the issue is fixed in `requests` we should not fail long
uploads: stop using advanced timeouts for now.

Also decreased FAST timeout from 10 to 8 so we are guaranteed to have
at least 3 tries with the 60s timeout on tasks GET loop.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority/high Issue to solve quickly

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Network upload fails after ~3s: requests.exceptions.ConnectionError: ('Connection aborted.', timeout('The write operation timed out',))

3 participants