@@ -3,14 +3,14 @@ Retryable Writes
3
3
================
4
4
5
5
:Spec Title: Retryable Writes
6
- :Spec Version: 1.5.2
6
+ :Spec Version: 1.5.3
7
7
:Author: Jeremy Mikola
8
8
:Lead: \A . Jesse Jiryu Davis
9
9
:Advisors: Robert Stam, Esha Maharishi, Samantha Ritter, and Kaloian Manassiev
10
10
:Status: Accepted
11
11
:Type: Standards
12
12
:Minimum Server Version: 3.6
13
- :Last Modified: 2020-02-25
13
+ :Last Modified: 2020-09-01
14
14
15
15
.. contents ::
16
16
@@ -226,9 +226,9 @@ configuration option set to true.
226
226
For server versions 4.4 and newer, MongoDB will add a RetryableWriteError label to
227
227
errors or server responses that it considers retryable before returning them to the
228
228
driver. As new server versions are released, the errors that are labeled with the
229
- RetryableWriteError label may change. When receiving a command result
230
- with an error from a 4.4+ server that supports retryable writes, the driver
231
- MUST NOT add a RetryableWriteError label to that error under any condition .
229
+ RetryableWriteError label may change. Drivers MUST NOT add a RetryableWriteError
230
+ label to any error derived from a 4.4+ server response (i.e. any error that is not
231
+ a network error) .
232
232
233
233
During a retryable write operation on a sharded cluster, mongos may retry the
234
234
operation internally, in which case it will not add a RetryableWriteError label to
@@ -807,6 +807,9 @@ inconsistent with the server and potentially confusing to developers.
807
807
Changes
808
808
=======
809
809
810
+ 2020-09-01: State the the driver should only add the RetryableWriteError label
811
+ to network errors when connected to a 4.4+ server.
812
+
810
813
2020-02-25: State that the driver should only add the RetryableWriteError label
811
814
when retryWrites is on, and make it clear that mongos will sometimes perform
812
815
internal retries and not return the RetryableWriteError label.
0 commit comments