-
Type:
Bug
-
Resolution: Incomplete
-
Priority:
Major - P3
-
None
-
Affects Version/s: 2.6.0-rc1
-
Component/s: Internal Client
-
None
-
ALL
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
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?
- related to
-
SERVER-12583 pcursor doesn't check the last used node status from ReplicaSetMonitor
-
- Closed
-