-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: Command Logging and Monitoring
-
None
-
Needed
-
Summary
DRIVERS-2877 attempted to fix racy unacknowledged write tests by following the write operation with a query:
Since connection pool size defaults to 1, the next operation will use the same connection, and won't complete until after completion of the unacknowledged write.
However, it neglected to add useMultipleMongoses: false to the client under test, which means it's possible that the query executes on a different mongos than the preceding unacknowledged write. This resulted in sporadic failures (see: PHPLIB-1461).
What is the problem or use case, what are we trying to achieve?
Motivation
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
- is related to
-
DRIVERS-2877 Fix racy unified tests of unacknowledged writes
- Implementing
- split to
-
CDRIVER-5597 Use single mongos in racy unacknowledged write tests
- Backlog
-
CXX-3045 Use single mongos in racy unacknowledged write tests
- Backlog
-
GODRIVER-3238 Use single mongos in racy unacknowledged write tests
- Backlog
-
RUBY-3486 Use single mongos in racy unacknowledged write tests
- Ready for Work
-
CSHARP-5120 Use single mongos in racy unacknowledged write tests
- Closed
-
JAVA-5491 Use single mongos in racy unacknowledged write tests
- Closed
-
MOTOR-1324 Use single mongos in racy unacknowledged write tests
- Closed
-
NODE-6202 Use single mongos in racy unacknowledged write tests
- Closed
-
PYTHON-4478 Use single mongos in racy unacknowledged write tests
- Closed
-
RUST-1964 Use single mongos in racy unacknowledged write tests
- Closed
-
PHPLIB-1461 unacknowledgedBulkWrite command monitoring test may fail on mongos
- Closed