-
Notifications
You must be signed in to change notification settings - Fork 531
Expand file tree
/
Copy pathhello-network-error.yml
More file actions
228 lines (221 loc) · 6.98 KB
/
hello-network-error.yml
File metadata and controls
228 lines (221 loc) · 6.98 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
---
description: hello-network-error
schemaVersion: "1.4"
runOnRequirements:
# Require SERVER-49336 for failCommand + appName on the initial handshake.
- minServerVersion: "4.4.7"
serverless: forbid
topologies: [ single, replicaset, sharded ]
createEntities:
- client:
id: &setupClient setupClient
useMultipleMongoses: false
initialData: &initialData
- collectionName: &collectionName hello-network-error
databaseName: &databaseName sdam-tests
documents: []
tests:
- description: Network error on Monitor handshake
# Configure the initial handshake to fail with a network error.
# Use times: 2 so that the RTT hello fails as well.
operations:
- name: failPoint
object: testRunner
arguments:
client: *setupClient
failPoint:
configureFailPoint: failCommand
mode:
times: 2
data:
failCommands:
- hello
- isMaster
appName: networkErrorHandshakeTest
closeConnection: true
- name: createEntities
object: testRunner
arguments:
entities:
- client:
id: &client client
useMultipleMongoses: false
observeEvents:
- commandStartedEvent
- serverDescriptionChangedEvent
- poolClearedEvent
uriOptions:
retryWrites: false
connectTimeoutMS: 250
heartbeatFrequencyMS: 500
appname: networkErrorHandshakeTest
- database:
id: &database database
client: *client
databaseName: *databaseName
- collection:
id: &collection collection
database: *database
collectionName: *collectionName
# The network error on the initial handshake should mark the server
# Unknown (emitting a ServerDescriptionChangedEvent) and clear the pool.
- name: waitForEvent
object: testRunner
arguments:
client: *client
event:
serverDescriptionChangedEvent:
newDescription:
type: Unknown
count: 1
# Perform an operation to ensure the node is discovered.
- name: insertMany
object: *collection
arguments:
documents:
- _id: 1
- _id: 2
# We cannot assert the server was marked Unknown and pool was cleared an
# exact number of times because the RTT hello may or may not have
# triggered this failpoint as well.
expectEvents:
- client: *client
eventType: command
events:
- commandStartedEvent:
command:
insert: hello-network-error
documents:
- _id: 1
- _id: 2
commandName: insert
databaseName: *databaseName
outcome:
- collectionName: *collectionName
databaseName: *databaseName
documents:
- _id: 1
- _id: 2
- description: Network error on Monitor check
skipReason: "RUBY-3781: Ruby driver's legacy_write_with_retry causes this to fail"
operations:
- name: createEntities
object: testRunner
arguments:
entities:
- client:
id: &client client
useMultipleMongoses: false
observeEvents:
- commandStartedEvent
- serverDescriptionChangedEvent
- poolClearedEvent
uriOptions:
retryWrites: false
connectTimeoutMS: 250
heartbeatFrequencyMS: 500
appname: networkErrorCheckTest
- database:
id: &database database
client: *client
databaseName: *databaseName
- collection:
id: &collection collection
database: *database
collectionName: *collectionName
# Perform an operation to ensure the node is discovered.
- name: insertMany
object: *collection
arguments:
documents:
- _id: 1
- _id: 2
# Configure the next streaming hello check to fail with a non-timeout
# network error. Use "times: 4" to increase the probability that the
# Monitor check fails since the RTT hello may trigger this failpoint one
# or many times as well.
- name: failPoint
object: testRunner
arguments:
failPoint:
configureFailPoint: failCommand
mode:
times: 2
data:
failCommands:
- hello
- isMaster
appName: networkErrorCheckTest
closeConnection: true
client: *setupClient
# The network error on the next check should mark the server Unknown and
# clear the pool.
- name: waitForEvent
object: testRunner
arguments:
client: *client
event:
serverDescriptionChangedEvent:
newDescription:
type: Unknown
count: 1
- name: waitForEvent
object: testRunner
arguments:
client: *client
event:
poolClearedEvent: {}
count: 1
# Perform an operation to ensure the node is rediscovered.
- name: insertMany
object: *collection
arguments:
documents:
- _id: 3
- _id: 4
# We cannot assert the server was marked Unknown and pool was cleared an
# exact number of times because the RTT hello may or may not have
# triggered this failpoint as well.
# - name: assertEventCount
# object: testRunner
# arguments:
# client: *client
# event:
# serverDescriptionChangedEvent:
# newDescription:
# type: Unknown
# count: 1
# - name: assertEventCount
# object: testRunner
# arguments:
# event:
# poolClearedEvent: {}
# count: 1
expectEvents:
- client: *client
eventType: command
events:
- commandStartedEvent:
command:
insert: hello-network-error
documents:
- _id: 1
- _id: 2
commandName: insert
databaseName: *databaseName
- commandStartedEvent:
command:
insert: hello-network-error
documents:
- _id: 3
- _id: 4
commandName: insert
databaseName: *databaseName
outcome:
- collectionName: *collectionName
databaseName: *databaseName
documents:
- _id: 1
- _id: 2
- _id: 3
- _id: 4