From 5d4ea3006358e247f5a0d648b05abe50eff88edc Mon Sep 17 00:00:00 2001 From: Preston Vasquez Date: Thu, 30 Jan 2025 09:43:59 -0700 Subject: [PATCH] DRIVERS-2868 Include min rtt in adjustment --- .../client-side-operations-timeout.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/client-side-operations-timeout/client-side-operations-timeout.md b/source/client-side-operations-timeout/client-side-operations-timeout.md index 16e2a7ab01..e0f3c6c371 100644 --- a/source/client-side-operations-timeout/client-side-operations-timeout.md +++ b/source/client-side-operations-timeout/client-side-operations-timeout.md @@ -337,7 +337,7 @@ If `timeoutMS` is set, drivers MUST apply it to the original operation. Drivers value to each `next` call on the resulting cursor. Helpers for operations that create tailable awaitData cursors MUST also support the `maxAwaitTimeMS` option. Drivers MUST error if this option is set, `timeoutMS` is set to a non-zero value, and `maxAwaitTimeMS` is greater than or equal to `timeoutMS`. If this option is set, drivers MUST use -`min(maxAwaitTimeMS, remaining timeoutMS)` as the `maxTimeMS` field on `getMore` commands. +`min(maxAwaitTimeMS, remaining timeoutMS - minRoundTripTime)` as the `maxTimeMS` field on `getMore` commands. See [Tailable cursor behavior](#tailable-cursor-behavior) for rationale regarding both non-awaitData and awaitData cursors.