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
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
|
runOn:
-
minServerVersion: "4.1.8"
topology: ["sharded"]
# serverless proxy doesn't use recovery tokens
serverless: "forbid"
database_name: &database_name "transaction-tests"
collection_name: &collection_name "test"
data: []
tests:
- description: commitTransaction explicit retries include recoveryToken
useMultipleMongoses: true
operations:
- name: startTransaction
object: session0
- name: insertOne
object: collection
arguments:
session: session0
document:
_id: 1
result:
insertedId: 1
- name: commitTransaction
object: session0
- name: commitTransaction
object: session0
- name: commitTransaction
object: session0
expectations:
- command_started_event:
command:
insert: *collection_name
documents:
- _id: 1
ordered: true
readConcern:
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction: true
autocommit: false
writeConcern:
command_name: insert
database_name: *database_name
- command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
writeConcern:
recoveryToken: 42
command_name: commitTransaction
database_name: admin
- command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
# commitTransaction applies w:majority on retries
writeConcern: { w: majority, wtimeout: 10000 }
recoveryToken: 42
command_name: commitTransaction
database_name: admin
- command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
# commitTransaction applies w:majority on retries
writeConcern: { w: majority, wtimeout: 10000 }
recoveryToken: 42
command_name: commitTransaction
database_name: admin
outcome:
collection:
data:
- _id: 1
- description: commitTransaction retry succeeds on new mongos
useMultipleMongoses: true
operations:
- name: startTransaction
object: session0
arguments:
options:
writeConcern:
w: majority
- name: insertOne
object: collection
arguments:
session: session0
document:
_id: 1
result:
insertedId: 1
# Enable the fail point only on the Mongos that session0 is pinned to.
- name: targetedFailPoint
object: testRunner
arguments:
session: session0
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["commitTransaction"]
writeConcernError:
code: 91
errmsg: Replication is being shut down
errorLabels: ["RetryableWriteError"]
# The client sees a retryable writeConcernError on the first
# commitTransaction due to the fail point but it actually succeeds on the
# server (SERVER-39346). The retry will succeed both on a new mongos and
# on the original.
- name: commitTransaction
object: session0
expectations:
- command_started_event:
command:
insert: *collection_name
documents:
- _id: 1
ordered: true
readConcern:
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction: true
autocommit: false
writeConcern:
command_name: insert
database_name: *database_name
- command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
writeConcern:
w: majority
recoveryToken: 42
command_name: commitTransaction
database_name: admin
- command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
# commitTransaction applies w:majority on retries
writeConcern: { w: majority, wtimeout: 10000 }
recoveryToken: 42
command_name: commitTransaction
database_name: admin
outcome:
collection:
data:
- _id: 1
- description: commitTransaction retry fails on new mongos
useMultipleMongoses: true
clientOptions:
# Increase heartbeatFrequencyMS to avoid the race condition where an in
# flight heartbeat refreshes the first mongoes' SDAM state in between
# the initial commitTransaction and the retry attempt.
heartbeatFrequencyMS: 30000
operations:
- name: startTransaction
object: session0
- name: insertOne
object: collection
arguments:
session: session0
document:
_id: 1
result:
insertedId: 1
# Enable the fail point only on the Mongos that session0 is pinned to.
# Fail hello/legacy hello to prevent the heartbeat requested directly after the
# retryable commit error from racing with server selection for the retry.
# Note: times: 7 is slightly artbitrary but it accounts for one failed
# commit and some SDAM heartbeats. A test runner will have multiple
# clients connected to this server so this fail point configuration
# is also racy.
- name: targetedFailPoint
object: testRunner
arguments:
session: session0
failPoint:
configureFailPoint: failCommand
mode: { times: 7 }
data:
failCommands: ["commitTransaction", "isMaster", "hello"]
closeConnection: true
# The first commitTransaction sees a retryable connection error due to
# the fail point and also fails on the server. The retry attempt on a
# new mongos will wait for the transaction to timeout and will fail
# because the transaction was aborted. Note that the retry attempt should
# not select the original mongos because that server's SDAM state is
# reset by the connection error, heartbeatFrequencyMS is high, and
# subsequent heartbeats should fail.
- name: commitTransaction
object: session0
result:
errorLabelsContain: ["TransientTransactionError"]
errorLabelsOmit: ["UnknownTransactionCommitResult"]
errorCodeName: NoSuchTransaction
expectations:
- command_started_event:
command:
insert: *collection_name
documents:
- _id: 1
ordered: true
readConcern:
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction: true
autocommit: false
writeConcern:
command_name: insert
database_name: *database_name
- command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
writeConcern:
recoveryToken: 42
command_name: commitTransaction
database_name: admin
- command_started_event:
command:
commitTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
# commitTransaction applies w:majority on retries
writeConcern: { w: majority, wtimeout: 10000 }
recoveryToken: 42
command_name: commitTransaction
database_name: admin
outcome:
collection:
data: []
- description: abortTransaction sends recoveryToken
useMultipleMongoses: true
operations:
- name: startTransaction
object: session0
- name: insertOne
object: collection
arguments:
session: session0
document:
_id: 1
result:
insertedId: 1
# Enable the fail point only on the Mongos that session0 is pinned to.
- name: targetedFailPoint
object: testRunner
arguments:
session: session0
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["abortTransaction"]
closeConnection: true
# The first abortTransaction sees a retryable connection error due to
# the fail point. The retry attempt on a new mongos will send the
# recoveryToken. Note that the retry attempt will also fail because the
# server does not yet support aborting from a new mongos, however this
# operation should "succeed" since abortTransaction ignores errors.
- name: abortTransaction
object: session0
expectations:
- command_started_event:
command:
insert: *collection_name
documents:
- _id: 1
ordered: true
readConcern:
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction: true
autocommit: false
writeConcern:
command_name: insert
database_name: *database_name
- command_started_event:
command:
abortTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
writeConcern:
recoveryToken: 42
command_name: abortTransaction
database_name: admin
- command_started_event:
command:
abortTransaction: 1
lsid: session0
txnNumber:
$numberLong: "1"
startTransaction:
autocommit: false
writeConcern:
recoveryToken: 42
command_name: abortTransaction
database_name: admin
outcome:
collection:
data: []
|
