Child Item

Frequent Timeouts (>4.5 minutes) during files_upload_session_append_v2

Hi,

I'm uploading larger files (up to 9.3 GiB) in 4 MiB chunks via the dropbox python library in an Azure function.
In the last few months they started failing very frequently because on some chunks the files_upload_session_append_v2 times out.

I increased the timeout to 4.5 minutes, but it still times out.

Since I'm uploading from an Azure data center I doubt this is an ISP issue.

Sometimes the chunk gets accepted by dropbox despite the timeout and sometimes not.
I'm trying to adapt my code for this, but at the same time would like to know if there is any throttling going on or any known issues on the dropbox side.

Thank you!

Find more posts tagged with

API

Abuse

Comments

Greg-DB

Thanks for the report! I'm not aware of anything that should be causing this, but we'll be happy to look into this. To help us investigate, please share the following:

the version number of Python you're using
the version number of the Dropbox Python SDK you're using
an estimate of the percent of these calls that fail
the full error output for a failed call
the output of a traceroute or tracert to content.dropboxapi.com from an affected machine

ITNETSYS

Hi Greg,

Thanks for replying.
Python version: 3.6.4 (v3.6.4:d48eceb, Dec 19 2017, 06:54:40) [MSC v.1900 64 bit (AMD64)]
Dropbox SDK version: 8.8.1

On the last 2330 calls I got 15 timeouts, so based on this limited data about 0.7% failure rate

I'm calling DBX.files_upload_session_append_v2(chunk, cursor) and I'll get a requests Timeout exception on a random chunk during that call.

Appaerently Azure web app service intances block ICMP. So I can't use Ping and Tracert, but here is a tcpping result:

PS \home> tcpping content.dropboxapi.com
tcpping content.dropboxapi.com
Connected to content.dropboxapi.com:80, time taken: 78ms
Connected to content.dropboxapi.com:80, time taken: 49ms
Connected to content.dropboxapi.com:80, time taken: <1ms
Connected to content.dropboxapi.com:80, time taken: 10ms
Complete: 4/4 successful attempts (100% ). Average success time: 34.25ms

Greg-DB

Thanks for following up. Can you share the actual error output though? The particular error type and stack trace may be helpful. Thanks in advance!