Summary

We have tests that verify that when timeoutMS is set to a non-zero value, operations can retry multiple times if retryWrites and retryReads are enabled. We should add tests to ensure that even if timeoutMS is set to a non-zero value, operations will not retry if retryWrites and/or retryReads are disabled.

Motivation

Who is the affected end user?

Eventual users of client side operations timeout.

How does this affect the end user?

Lack of test coverage could imply an inability to stop retrying as many times as possible with timeoutMS.

How likely is it that this problem or use case will occur?

Almost implemented un-escapable retrying in the Go driver (cannot be turned off with retryReads or retryWrites) without these tests.

If the problem does occur, what are the consequences and how severe are they?

Unexpected behavior.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Should be.