-
Type: Spec Change
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: SDAM
-
None
-
Needed
-
Summary
A test should be added to Heartbeat Tests to ensure that when serverMonitoringMode=poll, SDAM awaits the full heartbeatFrequency before handshaking with the server.
Motivation
An external user reported GODRIVER-3255 which describes a bug where the server is flooded with heartbeats when serverMonitoringMode=poll. The tests defined in DRIVERS-2578 do not cover this case.
Is this issue urgent?
No
Is this ticket required by a downstream team?
No
Is this ticket only for tests?
Yes
Acceptance Criteria
Generalize the prose test defined in mongodb/mongo-go-driver PR #1720.
- depends on
-
DRIVERS-2366 Convert SDAM integration spec tests to the unified test format
- Implementing
- is testing
-
DRIVERS-2578 Switch to polling monitoring when running within a FaaS environment
- Implementing
- split to
-
NODE-6303 Test serverMonitoringMode=poll waits after a successful heartbeat
- Backlog
-
CDRIVER-5647 Test serverMonitoringMode=poll waits after a successful heartbeat
- Backlog
-
GODRIVER-3295 Test serverMonitoringMode=poll waits after a successful heartbeat
- Backlog
-
JAVA-5564 Test serverMonitoringMode=poll waits after a successful heartbeat
- Backlog
-
RUST-2011 Test serverMonitoringMode=poll waits after a successful heartbeat
- Backlog
-
CXX-3084 Test serverMonitoringMode=poll waits after a successful heartbeat
- Blocked
-
PHPLIB-1497 Test serverMonitoringMode=poll waits after a successful heartbeat
- Blocked
-
RUBY-3527 Test serverMonitoringMode=poll waits after a successful heartbeat
- Blocked
-
CSHARP-5213 Test serverMonitoringMode=poll waits after a successful heartbeat
- Closed
-
MOTOR-1349 Test serverMonitoringMode=poll waits after a successful heartbeat
- Closed
-
PYTHON-4605 Test serverMonitoringMode=poll waits after a successful heartbeat
- Closed