blob: 5c5f364d58e9863da5c7eed94716a5d8fe4d5ac6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
|
runOn:
-
minServerVersion: "4.0"
topology: ["replicaset"]
-
minServerVersion: "4.1.8"
topology: ["sharded"]
database_name: &database_name "withTransaction-tests"
collection_name: &collection_name "test"
data: []
tests:
-
description: commitTransaction is retried after WriteConcernFailed timeout error
failPoint:
configureFailPoint: failCommand
mode: { times: 2 }
data:
failCommands: ["commitTransaction"]
# Do not specify closeConnection: false, since that would conflict
# with writeConcernError (see: SERVER-39292)
writeConcernError:
code: 64
codeName: WriteConcernFailed
errmsg: "waiting for replication timed out"
errInfo: { wtimeout: true }
operations:
- &operation
name: withTransaction
object: session0
arguments:
callback:
operations:
-
name: insertOne
object: collection
arguments:
session: session0
document: { _id: 1 }
result:
insertedId: 1
expectations: &expectations_with_retries
-
command_started_event:
command:
insert: *collection_name
documents:
- { _id: 1 }
ordered: true
lsid: session0
txnNumber: { $numberLong: "1" }
startTransaction: true
autocommit: false
# omitted fields
readConcern: ~
writeConcern: ~
command_name: insert
database_name: *database_name
-
command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber: { $numberLong: "1" }
autocommit: false
# omitted fields
readConcern: ~
startTransaction: ~
writeConcern: ~
command_name: commitTransaction
database_name: admin
-
command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber: { $numberLong: "1" }
autocommit: false
# commitTransaction applies w:majority on retries (SPEC-1185)
writeConcern: { w: majority, wtimeout: 10000 }
# omitted fields
readConcern: ~
startTransaction: ~
command_name: commitTransaction
database_name: admin
-
command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber: { $numberLong: "1" }
autocommit: false
# commitTransaction applies w:majority on retries (SPEC-1185)
writeConcern: { w: majority, wtimeout: 10000 }
# omitted fields
readConcern: ~
startTransaction: ~
command_name: commitTransaction
database_name: admin
# The write operation is still applied despite the write concern error
outcome: &outcome
collection:
data:
- { _id: 1 }
-
# This test configures the fail point to return an error with the
# WriteConcernFailed code but without errInfo that would identify it as a
# wtimeout error. This tests that drivers do not assume that all
# WriteConcernFailed errors are due to a replication timeout.
description: commitTransaction is retried after WriteConcernFailed non-timeout error
failPoint:
configureFailPoint: failCommand
mode: { times: 2 }
data:
failCommands: ["commitTransaction"]
# Do not specify closeConnection: false, since that would conflict
# with writeConcernError (see: SERVER-39292)
writeConcernError:
code: 64
codeName: WriteConcernFailed
errmsg: "multiple errors reported"
operations:
- *operation
expectations: *expectations_with_retries
outcome: *outcome
-
description: commitTransaction is not retried after UnknownReplWriteConcern error
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["commitTransaction"]
writeConcernError:
code: 79
codeName: UnknownReplWriteConcern
errmsg: "No write concern mode named 'foo' found in replica set configuration"
operations:
- <<: *operation
result:
errorCodeName: UnknownReplWriteConcern
errorLabelsOmit: ["TransientTransactionError", "UnknownTransactionCommitResult"]
expectations: &expectations_without_retries
-
command_started_event:
command:
insert: *collection_name
documents:
- { _id: 1 }
ordered: true
lsid: session0
txnNumber: { $numberLong: "1" }
startTransaction: true
autocommit: false
# omitted fields
readConcern: ~
writeConcern: ~
command_name: insert
database_name: *database_name
-
command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber: { $numberLong: "1" }
autocommit: false
# omitted fields
readConcern: ~
startTransaction: ~
writeConcern: ~
command_name: commitTransaction
database_name: admin
# failCommand with writeConcernError still applies the write operation(s)
outcome: *outcome
-
description: commitTransaction is not retried after UnsatisfiableWriteConcern error
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["commitTransaction"]
writeConcernError:
code: 100
codeName: UnsatisfiableWriteConcern
errmsg: "Not enough data-bearing nodes"
operations:
- <<: *operation
result:
errorCodeName: UnsatisfiableWriteConcern
errorLabelsOmit: ["TransientTransactionError", "UnknownTransactionCommitResult"]
expectations: *expectations_without_retries
# failCommand with writeConcernError still applies the write operation(s)
outcome: *outcome
-
description: commitTransaction is not retried after MaxTimeMSExpired error
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["commitTransaction"]
writeConcernError:
code: 50
codeName: MaxTimeMSExpired
errmsg: "operation exceeded time limit"
operations:
- <<: *operation
result:
errorCodeName: MaxTimeMSExpired
errorLabelsContain: ["UnknownTransactionCommitResult"]
errorLabelsOmit: ["TransientTransactionError"]
expectations: *expectations_without_retries
# failCommand with writeConcernError still applies the write operation(s)
outcome: *outcome
|
