When executing blob storage requests against azurite, our code occasionally hits the following exception that is bubbled up from the curl.cpp wrapper: "Connection was closed by the server while trying to read a response" - it seems that there could be three places, where this exception may be thrown. I have not managed to assemble a short code snippet to reproduce the issue, and we only observe this when running our emulated service against azurite.
What I see in practice when this issue happens:
- Many micro-services are talking in parallel to azurite.
- One of the services fails to communicate and freezes for roughly 30 seconds in a call to an azure-storage-blobs method. It eventually throws the exception above.
- I can consistently reproduce the issue on a call that looks as follows:
auto response = blobServiceClient->GetBlobContainerClient(container).GetBlobClient(name).Download();
response.Value.BodyStream->ReadToCount(
reinterpret_cast<uint8_t*>(val.data()), val.size());
but it also happens for other calls.
4. The corresponding request never shows up in the azurite logs, which might indicate in a (temp) failure to talk to azurite, etc.
5. I have never seen the same issue when running the same code against real Azure blob storage.
Please let me know, if I can help with more details. Unfortunately, I cannot share the actual source code to replicate the issue.
When executing blob storage requests against azurite, our code occasionally hits the following exception that is bubbled up from the
curl.cppwrapper: "Connection was closed by the server while trying to read a response" - it seems that there could be three places, where this exception may be thrown. I have not managed to assemble a short code snippet to reproduce the issue, and we only observe this when running our emulated service against azurite.What I see in practice when this issue happens:
but it also happens for other calls.
4. The corresponding request never shows up in the azurite logs, which might indicate in a (temp) failure to talk to azurite, etc.
5. I have never seen the same issue when running the same code against real Azure blob storage.
Please let me know, if I can help with more details. Unfortunately, I cannot share the actual source code to replicate the issue.