[SERVER-13125] DBClientRS should check that pinned hosts still match read preference Created: 10/Mar/14  Updated: 08/Jul/15  Resolved: 08/Jul/15

Status: Closed
Project: Core Server
Component/s: Internal Client
Affects Version/s: 2.6.0-rc1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Unassigned
Resolution: Incomplete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-12583 pcursor doesn't check the last used n... Closed
Operating System: ALL
Participants:

 Description   

Similar to SERVER-12583 which only checked for whether we thought the host was up or down. We should also check that other requirements of the read preference are still acceptable.

One complication that may need to be considered is what to do if there is now a "better" host that we should use. As an example if we were using PrimaryPreferred and settled for a secondary, should we unpin when a primary becomes available. What about hosts with lower ping times or that match an earlier tag predicate?


Generated at Thu Feb 08 03:30:42 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.