-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Unknown
-
None
-
Component/s: Backpressure
-
None
-
Needed
-
Summary
Test replica set deprioritization when a deprioritized server is the only server with a matching tag set.
Motivation
Motivated by a bug in the C driver: CDRIVER-6248
Who is the affected end user?
Users using read preferences with tag sets.
How does this affect the end user?
If this surfaces a bug, this could cause an incorrect server to be selected.
How likely is it that this problem or use case will occur?
IMO unlikely. This was an implementation bug in C. But I think it is worth syncing the new spec tests to check all drivers.
If the problem does occur, what are the consequences and how severe are they?
Unsure. This might distribute load in a different way than the user intended.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
Yes.
Acceptance Criteria
- Ensure a new tests fail on the C driver prior to the fix of
CDRIVER-6248.
- is testing
-
CDRIVER-6248 Fix check in server deprioritization retry
-
- Closed
-
-
DRIVERS-3344 Add support for server selection's deprioritized servers to all topologies
-
- Implementing
-
- split to
-
CSHARP-5901 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
CXX-3425 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
GODRIVER-3825 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
JAVA-6114 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
NODE-7458 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
PHPLIB-1797 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
PYTHON-5734 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
RUBY-3783 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
RUST-2370 Test deprioritized selection with tag sets
-
- Needs Triage
-
-
CDRIVER-6250 Test deprioritized selection with tag sets
-
- Closed
-