-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Expand file tree
/
Copy pathminPoolSize-error.yml
More file actions
126 lines (121 loc) · 3.74 KB
/
minPoolSize-error.yml
File metadata and controls
126 lines (121 loc) · 3.74 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
---
description: minPoolSize-error
schemaVersion: "1.4"
runOnRequirements:
# Require SERVER-49336 for failCommand + appName on the initial handshake.
- minServerVersion: "4.4.7"
serverless: forbid
topologies:
- single
createEntities:
- client:
id: &setupClient setupClient
useMultipleMongoses: false
initialData: &initialData
- collectionName: &collectionName sdam-minPoolSize-error
databaseName: &databaseName sdam-tests
documents: []
tests:
- description: Server error on minPoolSize background creation
operations:
# Configure the initial monitor handshake to succeed but the
# first or second background minPoolSize establishments to fail.
- name: failPoint
object: testRunner
arguments:
client: *setupClient
failPoint:
configureFailPoint: failCommand
mode:
skip: 3
data:
failCommands:
- hello
- isMaster
appName: SDAMminPoolSizeError
errorCode: 91
- name: createEntities
object: testRunner
arguments:
entities:
- client:
id: &client client
useMultipleMongoses: false
observeEvents:
- serverDescriptionChangedEvent
- poolClearedEvent
- poolReadyEvent
uriOptions:
heartbeatFrequencyMS: 10000
appname: SDAMminPoolSizeError
minPoolSize: 10
serverMonitoringMode: poll
serverSelectionTimeoutMS: 1000
- database:
id: &database database
client: *client
databaseName: *databaseName
- collection:
id: &collection collection
database: *database
collectionName: *collectionName
# Wait for monitor to succeed handshake and mark the pool as ready.
- name: waitForEvent
object: testRunner
arguments:
client: *client
event:
poolReadyEvent: {}
count: 1
# Background connection establishment ensuring minPoolSize should fail,
# causing the pool to be cleared.
- name: waitForEvent
object: testRunner
arguments:
client: *client
event:
poolClearedEvent: {}
count: 1
# The server should be marked as Unknown as part of this.
- name: waitForEvent
object: testRunner
arguments:
client: *client
event:
serverDescriptionChangedEvent:
newDescription:
type: Unknown
count: 1
# Executing a command should fail server selection due to not being able
# to find the primary.
- name: runCommand
object: *database
arguments:
command:
ping: {}
commandName: ping
expectError:
isError: true
# Disable the failpoint, allowing the monitor to discover the primary again.
- name: failPoint
object: testRunner
arguments:
failPoint:
configureFailPoint: failCommand
mode: "off"
client: *setupClient
# Perform an operation to ensure the node is discovered.
- name: runCommand
object: *database
arguments:
command:
ping: 1
commandName: ping
# Assert that the monitor discovered the primary and mark the pool as ready again.
- name: assertEventCount
object: testRunner
arguments:
client: *client
event:
poolReadyEvent: {}
count: 2