KurlesHS/rclone
1
0
Fork 0
forked from TrueCloudLab/rclone
Code Pull requests Activity

yandex: note --timeout increase needed for large files

Browse source 
See: https://forum.rclone.org/t/rclone-stucks-at-the-end-of-a-big-file-upload/8102
This commit is contained in:
Nick Craig-Wood 2018-12-29 08:40:45 +00:00
parent 3220acc729
commit 6f30427357
1 changed files with 13 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

13
docs/content/yandex.md
View file

@ -127,6 +127,19 @@ does not take any path arguments.
To view your current quota you can use the `rclone about remote:` To view your current quota you can use the `rclone about remote:`
command which will display your usage limit (quota) and the current usage. command which will display your usage limit (quota) and the current usage.
### Limitations ###
When uploading very large files (bigger than about 5GB) you will need
to increase the `--timeout` parameter. This is because Yandex pauses
(perhaps to calculate the MD5SUM for the entire file) before returning
confirmation that the file has been uploaded. The default handling of
timeouts in rclone is to assume a 5 minute pause is an error and close
the connection - you'll see `net/http: timeout awaiting response
headers` errors in the logs if this is happening. Setting the timeout
to twice the max size of file in GB should be enough, so if you want
to upload a 30GB file set a timeout of `2 * 30 = 60m`, that is
`--timeout 60m`.
<!--- autogenerated options start - DO NOT EDIT, instead edit fs.RegInfo in backend/yandex/yandex.go then run make backenddocs --> <!--- autogenerated options start - DO NOT EDIT, instead edit fs.RegInfo in backend/yandex/yandex.go then run make backenddocs -->
### Standard Options ### Standard Options