Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sync retryable reads with SDAM #1453

Merged
merged 2 commits into from
Aug 22, 2023
Merged

Sync retryable reads with SDAM #1453

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7a62315
Sync retryable reads with SDAM
prestonvasquez Aug 21, 2023
4017c48
Update changelog
prestonvasquez Aug 21, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions source/retryable-reads/retryable-reads.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down Expand Up @@ -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.
Expand Down
Loading