Summary

The Jira ticket addresses the behavior of timeoutMS=0 in the mongosh URI not overriding the server's defaultMaxTimeMS, while an explicit maxTimeMS(0) does. The issue is identified as intended behavior from the Node.js driver, where timeoutMS=0 means infinite client-side operation timeout and does not emit a maxTimeMS override unless explicitly set. The discussion references the CSOT specification and driver source code, noting a potential inconsistency with spec wording and suggesting documentation updates. The ticket is escalated to the drivers team for further review and possible action.

Diagnostic Symptoms

• timeoutMS=0 in mongosh URI does not override server defaultMaxTimeMS

Motivation

Who is the affected end user?

Users with CSOT-compatible drivers.

How does this affect the end user?

They are facing an unexpected behavior.

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

Edge case.

Is this ticket required by a downstream team?

No

Is this ticket only for tests?

No. It will be a changes to CSOT spec too.