azure-storage-azcopy: AzCopy 10.1.2 TLS Handshake Timeout on VM with Low Memory

Which version of the AzCopy was used?

Note: The version is visible when running AzCopy without any argument

AzCopy 10.1.2

Which platform are you using? (ex: Windows, Mac, Linux)

Azure VM size DS1_v2: Windows Server 2019 Datacenter version 1809 build 17763.437

What command did you run?

Note: Please remove the SAS to avoid exposing your credentials. If you cannot remember the exact command, please retrieve it from the beginning of the log file.

.\azcopy.exe copy "*.json" "https://REDACTED.blob.core.windows.net/memory?st=2019-05-22T00%3A17%3A13Z&se=2019-05-23T00%3A17%3A13Z&sp=racwl&sv=2018-03-28&sr=c&sig=REDACTED" --overwrite=false --from-to=LocalBlob --blob-type=BlockBlob --put-md5;

What problem was encountered?

On an Azure size DS1_v2 VM running the latest stock Server 2019 image provided by Microsoft the command above does not run. Here’s some relevant output from the logs:

2019/05/22 01:08:23 ==> REQUEST/RESPONSE (Try=1/3m59.8699959s[SLOW >3s], OpTime=3m59.8699959s) -- REQUEST ERROR
   PUT https://REDACTED.blob.core.windows.net/memory/memdumptest-20190522-003248.json?se=2019-05-23t00%3A17%3A13z&sig=REDACTED&sp=racwl&sr=c&st=2019-05-22t00%3A17%3A13z&sv=2018-03-28&timeout=901
   Content-Length: [1504]
   User-Agent: [AzCopy/10.1.2 Azure-Storage/0.6 (go1.10.8; Windows_NT)]
   X-Ms-Blob-Cache-Control: []
   X-Ms-Blob-Content-Disposition: []
   X-Ms-Blob-Content-Encoding: []
   X-Ms-Blob-Content-Language: []
   X-Ms-Blob-Content-Md5: []
   X-Ms-Blob-Content-Type: [application/json]
   X-Ms-Blob-Type: [BlockBlob]
   X-Ms-Client-Request-Id: [01297009-16c5-46af-5bdb-fcecc71b69f0]
   X-Ms-Version: [2018-03-28]
   --------------------------------------------------------------------------------
   ERROR:
-> github.com/Azure/azure-storage-azcopy/vendor/github.com/Azure/azure-pipeline-go/pipeline.NewError, /go/src/github.com/Azure/azure-storage-azcopy/vendor/github.com/Azure/azure-pipeline-go/pipeline/error.go:154
HTTP request failed

Put https://REDACTED.blob.core.windows.net/memory/memdumptest-20190522-003248.json?se=2019-05-23T00%3A17%3A13Z&sig=REDACTED%3D&sp=racwl&sr=c&st=2019-05-22T00%3A17%3A13Z&sv=2018-03-28&timeout=901: net/http: TLS handshake timeout

How can we reproduce the problem in the simplest way?

Deploy an Azure DS1_v2 VM and run the command on it. It’ll fail. I’ve reproduced this on two DS1_v2 VMs.

Have you found a mitigation/solution?

If I run this same command on a VM with 8GB memory llike the B2ms AzCopy executes successfully. It looks like running the latest version of AzCopy on a system with low memory causes TLS handshakes to fail. It’s possible that other operations are failing on a system with low memory, too, I just can’t get past the handshake failures to see what else may be broken.

It looks like AzCopy has undocumented minimum system hardware requirements.