-
Type: Bug
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Server Selection
-
Needed
-
Summary
The operationCount based selection prose test in the server selection spec has proven to fail occasionally due to random slowness in in one of the mongoses. This is likely due to the mongoses competing for resources on the same virtual host (which is itself competing for resources). The C# and Rust driver teams have experimented with modifying this test to reduce the failures to some success. We should include these modifications in the actual spec so that future teams will not experience the same failures.
Motivation
Who is the affected end user?
Drivers teams
How does this affect the end user?
Their tests occasionally fail
How likely is it that this problem or use case will occur?
The test fails 1-2% of the time
Is this ticket only for tests?
Yes
- split to
-
CSHARP-3882 Server selection load balancing algorithm prose test is flaky
- Backlog
-
CXX-2379 Server selection load balancing algorithm prose test is flaky
- Backlog
-
RUBY-2799 Server selection load balancing algorithm prose test is flaky
- Closed
-
GODRIVER-2166 Server selection load balancing algorithm prose test is flaky
- Closed
-
MOTOR-823 Server selection load balancing algorithm prose test is flaky
- Closed
-
PHPLIB-727 Server selection load balancing algorithm prose test is flaky
- Closed
-
CDRIVER-4170 Server selection load balancing algorithm prose test is flaky
- Backlog
-
PYTHON-2924 Server selection load balancing algorithm prose test is flaky
- Closed
-
JAVA-4320 Server selection load balancing algorithm prose test is flaky
- Backlog
-
NODE-3638 Server selection load balancing algorithm prose test is flaky
- Closed
-
RUST-1035 Server selection load balancing algorithm prose test is flaky
- Closed