SDK Does Not Respect Configured Timeout

We are continuously addressing and improving the SDK, if possible, make sure the problem persist in the latest SDK version.

Describe the bug In the case of ServiceUnavailable (503) error when querying database, the SDK doesn’t respect the configured timeout. Timeout is configured during client initialization using CosmosClientOptions.RequestTimeout property.

CosmosClientOptions cosmosClientOptions = new CosmosClientOptions() { RequestTimeout = 500 };

To Reproduce

Expected behavior SDK should terminate the call and return control to the caller once request time exceeds the configured timeout.

Actual behavior SDK doesn’t terminate the call and blocks the caller for much more time than what it is configured during client initialization.

Environment summary SDK Version: cosmos-netstandard-sdk/3.23.1 OS Version Windows/10.0.17763

Additional context cosmosDbClientLogs.txt

[aavasthy]

@aavasthy, that means in 5 seconds the caller should have received an exception. But that did not happen. As you can see in the log, the request was blocked for at least 35 seconds (It may have been more than this).

@Jasen-Quadras when you say at least 35s(2100 ms) are you mentioning the total “duration in milliseconds”:34491.8583 that we see in the summary diagnostics?

[ealsur]

@aavasthy Can you take a look at the attached diagnostics and reply to this question?