From 3ff380031d7f4295335f0d63585acf24c96f8d7b Mon Sep 17 00:00:00 2001 From: Preston Vasquez Date: Tue, 22 Aug 2023 13:40:20 -0600 Subject: [PATCH] Sync retryable reads with SDAM (#1453) --- source/retryable-reads/retryable-reads.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/source/retryable-reads/retryable-reads.rst b/source/retryable-reads/retryable-reads.rst index 9d8eabb8cd..db9b1ddf28 100644 --- a/source/retryable-reads/retryable-reads.rst +++ b/source/retryable-reads/retryable-reads.rst @@ -614,10 +614,9 @@ The spec concerns itself with retrying read operations that encounter a retryable error (i.e. no response due to network error or a response indicating that the node is no longer a primary). A retryable error may be classified as either a transient error (e.g. dropped connection, replica set failover) or -persistent outage. In the case of a transient error, the driver will mark the -server as "unknown" per the `SDAM`_ -spec. A subsequent retry attempt will allow the driver to rediscover the primary -within the designated server selection timeout period (30 seconds by +persistent outage. If a transient error results in the server being marked as +"unknown", a subsequent retry attempt will allow the driver to rediscover the +primary within the designated server selection timeout period (30 seconds by default). If server selection times out during this retry attempt, we can reasonably assume that there is a persistent outage. In the case of a persistent outage, multiple retry attempts are fruitless and would waste time. See `How To @@ -679,6 +678,7 @@ degraded performance can simply disable ``retryableReads``. Changelog ========= +:2023-08-21: Update Q&A that contradicts SDAM transient error logic :2022-11-09: CLAM must apply both events and log messages. :2022-10-18: When CSOT is enabled multiple retry attempts may occur. :2022-10-05: Remove spec front matter, move footnote, and reformat changelog.