[DRIVERS-2563] Add spec test which checks that the order of read preference tag matching is obeyed Created: 27/Feb/23 Updated: 19/Sep/23 |
|
| Status: | Backlog |
| Project: | Drivers |
| Component/s: | Server Selection |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Max Hirschhorn | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Driver Changes: | Not Needed | ||||||||
| Description |
SummaryAdd spec test which checks that the order of read preference tag matching is obeyed. Motivation
From what I found in the existing driver spec tests the only tests I found using multiple tag sets are either (a) for testing maxStalenessSeconds is obeyed or (b) uses a "doesntexist" tag which don't match any of the servers anyway.
Who is the affected end user?Authors of drivers behavior on Drivers and Sharding team (mongos is driver-like). How does this affect the end user?Specification was misunderstood on Sharding team. How likely is it that this problem or use case will occur?This problem did happen (twice independently even, in both the scanning replica set monitor and in the new streamable replica set monitor). Read preference tags are commonly used in Atlas for ANALYTICS nodes and other resource separation strategies. If the problem does occur, what are the consequences and how severe are they?If the read preference tag matching isn't obeyed then applications will see queries they intended to target a constrained set of hosts going more commonly spread across all hosts and not only going to other hosts when the most preferred set of hosts are unavailable. Is this issue urgent?Not urgent. Is this ticket required by a downstream team?Not required by a downstream team. Is this ticket only for tests?Yes only for tests. |
| Comments |
| Comment by Max Hirschhorn [ 27/Feb/23 ] |
|
The sdam_tests and server_selection_tests were integrated into the server's automated testing. |
| Comment by Jeffrey Yemin [ 27/Feb/23 ] |
|
max.hirschhorn@mongodb.com which spec tests were integrated into the server's automated testing? I'm assuming the unit tests for the server selection spec, but pls confirm. |