[DRIVERS-2828] Update prose tests for mongos deprioritization during retryable ops Created: 06/Feb/24  Updated: 06/Feb/24

Status: In Review
Project: Drivers
Component/s: Performance, Retryability, Server Selection
Fix Version/s: None

Type: Task Priority: Unknown
Reporter: Ezra Chung Assignee: Ezra Chung
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Issue split
split to CSHARP-4958 Update prose tests for mongos deprior... Blocked
split to CXX-2824 Update prose tests for mongos deprior... Blocked
split to GODRIVER-3121 Update prose tests for mongos deprior... Blocked
split to JAVA-5320 Update prose tests for mongos deprior... Blocked
split to MOTOR-1252 Update prose tests for mongos deprior... Blocked
split to NODE-5905 Update prose tests for mongos deprior... Blocked
split to PHPLIB-1391 Update prose tests for mongos deprior... Blocked
split to PYTHON-4203 Update prose tests for mongos deprior... Blocked
split to RUBY-3391 Update prose tests for mongos deprior... Blocked
split to RUST-1842 Update prose tests for mongos deprior... Blocked
split to CDRIVER-4827 Update prose tests for mongos deprior... In Code Review
Related
is related to DRIVERS-1571 Direct read/write retries to another ... Implementing
Driver Changes: Needed - No Spec Changes
Start date:
Driver Compliance:
Key Status/Resolution FixVersion
CDRIVER-4827 In Code Review
CXX-2824 Blocked
CSHARP-4958 Blocked
GODRIVER-3121 Blocked
JAVA-5320 Blocked
NODE-5905 Blocked
MOTOR-1252 Blocked
PYTHON-4203 Blocked
PHPLIB-1391 Blocked
RUBY-3391 Blocked
RUST-1842 Blocked

 Description   

Summary

Prose tests introduced by DRIVERS-1571 may not execute relevant code paths due to (1) SDAM error handling behavior preceeding suitable server deprioritization and (2) Driver-specific SDAM behavior preventing deduction of a single-mongos connection as a Sharded topology.

Drivers that have already implemented DRIVERS-1571 should update their prose tests accordingly to the new prose test specification; Drivers that have not yet implemented DRIVERS-1571 should implement the prose tests according to the updated specification. Drivers are encouraged to confirm that the updated prose tests correctly execute the code paths related to server deprioritization using debuggers, code coverage tools, etc.

Motivation

Who is the affected end user?

Drivers implementing DRIVERS-1571.

How does this affect the end user?

Prose tests intended to test mongos redirection may not execute related code paths, potentially leading to false-positive test results for incorrect implementation of server deprioritization.

How likely is it that this problem or use case will occur?

Testing only.

If the problem does occur, what are the consequences and how severe are they?

Potential false-positive test results may allow incorrect server deprioritization implementations to slip into Drivers releases and fail to satisfy the requirements of customer requests in DRIVERS-1571.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

Yes (but may lead to changes to Drivers implementations if removal of potential false-positives uncovers proper test failures).

Acceptance Criteria

N/A


Generated at Thu Feb 08 08:26:29 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.