/
replaceOne-serverErrors.yml
82 lines (80 loc) · 2.44 KB
/
replaceOne-serverErrors.yml
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
runOn:
-
minServerVersion: "4.0"
topology: ["replicaset"]
-
minServerVersion: "4.1.7"
topology: ["sharded", "load-balanced"]
data:
- { _id: 1, x: 11 }
- { _id: 2, x: 22 }
tests:
-
description: "ReplaceOne succeeds after PrimarySteppedDown"
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["update"]
errorCode: 189
errorLabels: ["RetryableWriteError"]
operation:
name: "replaceOne"
arguments:
filter: { _id: 1 }
replacement: { _id: 1, x: 111 }
outcome:
result:
matchedCount: 1
modifiedCount: 1
upsertedCount: 0
collection:
data:
- { _id: 1, x: 111 }
- { _id: 2, x: 22 }
-
description: "ReplaceOne succeeds after WriteConcernError ShutdownInProgress"
failPoint:
configureFailPoint: failCommand
mode: { times: 1 }
data:
failCommands: ["update"]
writeConcernError:
code: 91
errmsg: Replication is being shut down
errorLabels: ["RetryableWriteError"]
operation:
name: "replaceOne"
arguments:
filter: { _id: 1 }
replacement: { _id: 1, x: 111 }
outcome:
result:
matchedCount: 1
modifiedCount: 1
upsertedCount: 0
collection:
data:
- { _id: 1, x: 111 }
- { _id: 2, x: 22 }
-
description: "ReplaceOne fails with a RetryableWriteError label after two connection failures"
failPoint:
configureFailPoint: failCommand
mode: { times: 2 }
data:
failCommands: ["update"]
closeConnection: true
operation:
name: "replaceOne"
arguments:
filter: { _id: 1 }
replacement: { _id: 1, x: 111 }
outcome:
error: true
result:
errorLabelsContain: ["RetryableWriteError"]
collection:
data:
- { _id: 1, x: 11 }
- { _id: 2, x: 22 }