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

Download stream interrupted #24636

Closed
cheryl-catalog opened this issue May 27, 2022 · 8 comments
Closed

Download stream interrupted #24636

cheryl-catalog opened this issue May 27, 2022 · 8 comments
Assignees
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. Storage Storage Service (Queues, Blobs, Files)

Comments

@cheryl-catalog
Copy link

/unresolved
I am seeing this error as well:

2022-05-27T21:51:42+0000 next():186 Unable to stream download: ("Connection broken: ConnectionResetError(104, 'Connection reset by peer')", ConnectionResetError(104, 'Connection reset by peer'))
2022-05-27T21:51:42+0000 wrapped():79 Download stream interrupted.

pip3 freeze | grep azure
azure-common==1.1.28
azure-core==1.24.0
azure-storage-blob==12.12.0
azure-storage-common==2.1.0
azure-storage-file==2.1.0
azure-storage-file-share==12.8.0

I will try the suggested tweaks in (#19753) and see how it goes. I just started seeing this error this week

Originally posted by @cheryl-catalog in #19753 (comment)

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 27, 2022
@azure-sdk azure-sdk added Client This issue points to a problem in the data-plane of the library. needs-team-triage Workflow: This issue needs the team to triage. Storage Storage Service (Queues, Blobs, Files) labels May 27, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label May 27, 2022
@catalinaperalta catalinaperalta added bug This issue requires a change to an existing behavior in the product in order to be resolved. CXP Attention labels May 31, 2022
@ghost
Copy link

ghost commented May 31, 2022

Thank you for your feedback. This has been routed to the support team for assistance.

@catalinaperalta catalinaperalta removed needs-team-triage Workflow: This issue needs the team to triage. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels May 31, 2022
@catalinaperalta
Copy link
Member

Thanks for reporting this @cheryl-catalog! We'll investigate asap.

@vincenttran-msft vincenttran-msft self-assigned this May 31, 2022
@jasonoberme
Copy link

Same here.

azure-core==1.22.1
azure-identity==1.7.1
azure-storage-blob==12.9.0

@jalauzon-msft
Copy link
Member

Hi @cheryl-catalog Cheryl / @jasonoberme, apologies for the delay in response.

Connection reset errors come from the Storage service and there is not much we can do on the client-side except retry. The client should be automatically retrying these errors and that usually will lead to a successful request, but we recently identified an issue with our retry logic, specifically when streaming large downloads and we have a fix coming in our next release, 12.14.0. (The preview should be released this month with the full release sometime in September). It is difficult to tell if this fix will help in your scenario but download streaming is the targeted feature.

If you are still experiencing the issue, could you include a full stack trace of the error if possible? That will help us identify if the upcoming fix will help.

Additionally, if you are seeing these pretty consistently, I would also recommend opening a support ticket so the service team can take a look. There can sometimes be issues on the backend that could cause these types of errors if they are happening consistently.

@cheryl-catalog
Copy link
Author

cheryl-catalog commented Aug 10, 2022 via email

@jalauzon-msft
Copy link
Member

Hi @cheryl-catalog Cheryl, azure-storage-blob 12.14.0 was released last week which contains the fixes I was mentioning w.r.t. streaming download retry. Could you try your test scenario again to see if the updates helped with the connection resets at all? Thanks.

@xiangyan99 xiangyan99 added the issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. label Oct 20, 2022
@ghost
Copy link

ghost commented Oct 20, 2022

Hi @cheryl-catalog. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

@ghost
Copy link

ghost commented Oct 27, 2022

Hi @cheryl-catalog, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.

@ghost ghost closed this as completed Oct 27, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug This issue requires a change to an existing behavior in the product in order to be resolved. Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. issue-addressed Workflow: The Azure SDK team believes it to be addressed and ready to close. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

7 participants