Use Case

Currently, `topology.selectServer` instantiates its own timeout context using `timeoutMS` from the client options when running `ping`. In the case of auto connect, this can result in an operation taking up to operation timeoutMS + client timeoutMS.

User Impact

• What is the number of impacted customers? How severe is the impact? Is anyone blocked or broken?

Dependencies

• upstream and/or downstream requirements and timelines to bear in mind

Unknowns

• questions that need to be answered to determine implementation

Acceptance Criteria

Implementation Requirements

1. Determine the desired behavior for CSOT with auto connect.
   1. Should operation timeoutMS govern auto connect, or should the ping be governed by client timeoutMS?
2. If necessary, align the implementation to match the outcome of 1.

Testing Requirements

• unit test, spec test sync, etc

Documentation Requirements

• DOCSP ticket, API docs, etc

Follow Up Requirements

• additional tickets to file, required releases, etc