Skip to content

[Storage][Perfstress] Datalake uploading in parallel can cause crash #16085

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

Closed
annatisch opened this issue Jan 11, 2021 · 1 comment
Closed
Labels
Client This issue points to a problem in the data-plane of the library. pillar-performance The issue is related to performance, one of our core engineering pillars. Storage Storage Service (Queues, Blobs, Files)

Comments

@annatisch
Copy link
Member

When running the datalake upload perf tests (Upload + UploadFromFile) in high levels (16+) of parallel threads or coroutines - we see instability in Python.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 11, 2021
@annatisch annatisch added pillar-performance The issue is related to performance, one of our core engineering pillars. Storage Storage Service (Queues, Blobs, Files) labels Jan 11, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 11, 2021
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-python that referenced this issue Sep 22, 2021
[Device Update for IoT Hub] Added Private Endpoint Connection API and model definitions (Azure#16085)

* Added Private Endpoint Connection API and model definitions, fixed minor errors

* Referenced common private link types

* Reference list types do not have nextLink property

* Fixed copy&paste description error

* Trying to suppress an error

* Change common types version to v3

* Suppression not working

* Extended common type in order to add a required property
@lmazuel lmazuel added the Client This issue points to a problem in the data-plane of the library. label Dec 17, 2021
Copy link

Hi @annatisch, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 15, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. pillar-performance The issue is related to performance, one of our core engineering pillars. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

2 participants