-
Notifications
You must be signed in to change notification settings - Fork 132
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
A transfer hangs when two processes use Data Movement Library #290
Comments
Linux image on which the test was performed: Standard D4s v3 (4 vcpus, 16 GiB memory) |
For Windows a developer laptop was used with the following parameters:Processor Intel(R) Xeon(R) E-2276M CPU @ 2.80GHz 2.81 GHz |
Issue is also reproducible using single process, this happens very occasionally, I would say randomly, but still.. |
We were able to implement a workaround in our fork, by adding a timeout for waiting in the method But to really unblock the transfer inside the same process, we needed to do two more things after our timeout occurs:
Our tests show it works, but... Please let us know if you see any risks connected to the above solution, because the changes occurred to be more invasive that we thought at the beginning and agreed during discussions with Microsoft team. |
Which service(blob, file) does this issue concern?
Blob (not tested for file)
Which version of the SDK was used?
2.0.4
On which platform were you using? (.Net Framework version or .Net Core version, and OS version)
.NET Core (not tested on .NET Framework)
How can the problem be reproduced? It'd be better if the code caused the problem can be shared.
ParallelOperations
. Sample code: DmLibThinClient.zipWhat problem was encountered?
FlatDirectoryTransfer.CheckAndPauseEnumeration()
and the value ofoutstandingTasks
doesn't change and exceedsMaxTransferConcurrency
.Have you found a mitigation/solution?
No. Also resetting the transfer is not a viable solution for us, as we use DMLib in automated workflows for long-running transfers.
The text was updated successfully, but these errors were encountered: