-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Expand file tree
/
Copy pathcommit-writeconcernerror.yml
More file actions
248 lines (243 loc) · 8.85 KB
/
commit-writeconcernerror.yml
File metadata and controls
248 lines (243 loc) · 8.85 KB
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
description: commit-writeconcernerror
schemaVersion: '1.3'
runOnRequirements:
- minServerVersion: '4.0'
topologies: [ replicaset ]
- minServerVersion: 4.1.8
topologies: [ sharded, load-balanced ]
createEntities:
- client:
id: &client0 client0
useMultipleMongoses: false
observeEvents: [ commandStartedEvent ]
- database:
id: &database0 database0
client: *client0
databaseName: &databaseName withTransaction-tests
- collection:
id: &collection0 collection0
database: *database0
collectionName: &collectionName test
- session:
id: &session0 session0
client: *client0
initialData:
- collectionName: *collectionName
databaseName: *databaseName
documents: []
tests:
-
description: commitTransaction is retried after WriteConcernTimeout timeout error
operations:
- name: failPoint
object: testRunner
arguments:
client: *client0
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
errmsg: "waiting for replication timed out"
errInfo: { wtimeout: true }
- &operation
name: withTransaction
object: *session0
arguments:
callback:
- name: insertOne
object: *collection0
arguments:
session: *session0
document: { _id: 1 }
expectResult:
$$unsetOrMatches: { insertedId: { $$unsetOrMatches: 1 } }
expectEvents: &expectEvents_with_retries
- client: *client0
events:
- commandStartedEvent:
command:
insert: *collectionName
documents:
- { _id: 1 }
ordered: true
lsid: { $$sessionLsid: *session0 }
txnNumber: { $numberLong: "1" }
startTransaction: true
autocommit: false
# omitted fields
readConcern: { $$exists: false }
writeConcern: { $$exists: false }
commandName: insert
databaseName: *databaseName
- commandStartedEvent:
command:
commitTransaction: 1
lsid: { $$sessionLsid: *session0 }
txnNumber: { $numberLong: "1" }
autocommit: false
# omitted fields
readConcern: { $$exists: false }
startTransaction: { $$exists: false }
writeConcern: { $$exists: false }
commandName: commitTransaction
databaseName: admin
- commandStartedEvent:
command:
commitTransaction: 1
lsid: { $$sessionLsid: *session0 }
txnNumber: { $numberLong: "1" }
autocommit: false
# commitTransaction applies w:majority on retries (SPEC-1185)
writeConcern: { w: majority, wtimeout: 10000 }
# omitted fields
readConcern: { $$exists: false }
startTransaction: { $$exists: false }
commandName: commitTransaction
databaseName: admin
- commandStartedEvent:
command:
commitTransaction: 1
lsid: { $$sessionLsid: *session0 }
txnNumber: { $numberLong: "1" }
autocommit: false
# commitTransaction applies w:majority on retries (SPEC-1185)
writeConcern: { w: majority, wtimeout: 10000 }
# omitted fields
readConcern: { $$exists: false }
startTransaction: { $$exists: false }
commandName: commitTransaction
databaseName: admin
# The write operation is still applied despite the write concern error
outcome: &outcome
- collectionName: *collectionName
databaseName: *databaseName
documents:
- { _id: 1 }
-
# This test configures the fail point to return an error with the
# WriteConcernTimeout code but without errInfo that would identify it as a
# wtimeout error. This tests that drivers do not assume that all
# WriteConcernTimeout errors are due to a replication timeout.
description: commitTransaction is retried after WriteConcernTimeout non-timeout error
operations:
- name: failPoint
object: testRunner
arguments:
client: *client0
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
errmsg: "multiple errors reported"
- *operation
expectEvents: *expectEvents_with_retries
outcome: *outcome
-
description: commitTransaction is not retried after UnknownReplWriteConcern error
operations:
- name: failPoint
object: testRunner
arguments:
client: *client0
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"
- <<: *operation
expectError:
errorCodeName: UnknownReplWriteConcern
errorLabelsOmit: ["TransientTransactionError", "UnknownTransactionCommitResult"]
expectEvents: &expectEvents_without_retries
- client: *client0
events:
- commandStartedEvent:
command:
insert: *collectionName
documents:
- { _id: 1 }
ordered: true
lsid: { $$sessionLsid: *session0 }
txnNumber: { $numberLong: "1" }
startTransaction: true
autocommit: false
# omitted fields
readConcern: { $$exists: false }
writeConcern: { $$exists: false }
commandName: insert
databaseName: *databaseName
- commandStartedEvent:
command:
commitTransaction: 1
lsid: { $$sessionLsid: *session0 }
txnNumber: { $numberLong: "1" }
autocommit: false
# omitted fields
readConcern: { $$exists: false }
startTransaction: { $$exists: false }
writeConcern: { $$exists: false }
commandName: commitTransaction
databaseName: admin
# failCommand with writeConcernError still applies the write operation(s)
outcome: *outcome
-
description: commitTransaction is not retried after UnsatisfiableWriteConcern error
operations:
- name: failPoint
object: testRunner
arguments:
client: *client0
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: [ commitTransaction ]
writeConcernError:
code: 100
codeName: UnsatisfiableWriteConcern
errmsg: "Not enough data-bearing nodes"
- <<: *operation
expectError:
errorCodeName: UnsatisfiableWriteConcern
errorLabelsOmit: ["TransientTransactionError", "UnknownTransactionCommitResult"]
expectEvents: *expectEvents_without_retries
# failCommand with writeConcernError still applies the write operation(s)
outcome: *outcome
-
description: commitTransaction is not retried after MaxTimeMSExpired error
operations:
- name: failPoint
object: testRunner
arguments:
client: *client0
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: [ commitTransaction ]
writeConcernError:
code: 50
codeName: MaxTimeMSExpired
errmsg: "operation exceeded time limit"
- <<: *operation
expectError:
errorCodeName: MaxTimeMSExpired
errorLabelsContain: ["UnknownTransactionCommitResult"]
errorLabelsOmit: ["TransientTransactionError"]
expectEvents: *expectEvents_without_retries
# failCommand with writeConcernError still applies the write operation(s)
outcome: *outcome