Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'ReadTimeoutError' when accessing Azure Blob Storage in azure ml workspace #680

Open
pwyang123 opened this issue Sep 30, 2020 · 0 comments

Comments

@pwyang123
Copy link

pwyang123 commented Sep 30, 2020

Which service(blob, file, queue) does this issue concern?

Note: for package version >= 12.0.0 please post the issue here instead: https://github.com/Azure/azure-sdk-for-python/issues
      for table service, please post the issue here instead: https://github.com/Azure/azure-cosmosdb-python.

blob

Which version of the SDK was used? Please provide the output of pip freeze.

azureml-core==1.13.0 azureml-dataprep==2.0.1.

What problem was encountered?

when accessing Azure Blob Storage in azure ml workspace, repetitive warnings about connection, which become bottleneck of running. The typical warning message is as the following:

urllib3.connectionpool][WARNING] - Retrying (Retry(total=2, connect=3, read=2, redirect=None, status=None)) after connection broken by 'ReadTimeoutError('HTTPSConnectionPool(host='****.blob.core.windows.net', port=443): Read timed out. (read timeout=120)',)': /azureml/ExperimentRun/...

Inputs on how to solve the issue? And is there any way to customize retry policy of access, and to increase the read timeout (currently 120) and to increase connectionpool (currently (total=2, connect=3, read=2, redirect=None, status=None))?

Have you found a mitigation/solution?

Not yet.

@pwyang123 pwyang123 changed the title 'ReadTimeoutError' during am 'ReadTimeoutError' when accessing Azure Blob Storage in azure ml workspace Sep 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant