-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Backpressure
-
None
-
Needed
-
Summary
backpressure-network-error-fail andĀ backpressure-network-timeout-error tests are racy on non-standalone topology. Configuring failPoint for hello after the first succeded heartbeat could be flaky, because first heartbeat to succeed could be from non-primary node.
Motivation
Is this ticket only for tests?
Yes.
- related to
-
DRIVERS-3218 Avoid clearing the connection pool when the server connection rate limiter triggers
-
- Implementing
-
- split to
-
CDRIVER-6196 Fix racy backpressure-network-* tests
-
- Needs Triage
-
-
CXX-3398 Fix racy backpressure-network-* tests
-
- Needs Triage
-
-
GODRIVER-3758 Fix racy backpressure-network-* tests
-
- Needs Triage
-
-
RUBY-3756 Fix racy backpressure-network-* tests
-
- Needs Triage
-
-
RUST-2336 Fix racy backpressure-network-* tests
-
- Needs Triage
-
-
NODE-7367 Fix racy backpressure-network-* tests
-
- Backlog
-
-
CSHARP-5834 Fix racy backpressure-network-* tests
-
- In Code Review
-
-
PYTHON-5696 Fix racy backpressure-network-* tests
-
- In Code Review
-
-
JAVA-6056 Fix racy backpressure-network-* tests
-
- In Progress
-
-
PHPLIB-1767 Fix racy backpressure-network-* tests
-
- Closed
-