[SERVER-12232] cached connections to secondary are not validated against the global ReplicaSetMonitor before using Created: 02/Jan/14 Updated: 06/Dec/22 Resolved: 27/Oct/16 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Client |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Greg Studer | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | cxxcopy | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Sharding
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Before creating a new connection to a secondary host, a DBClientReplicaSet connection tries to re-use a previously cached connection to a secondary host. This connection may still exist, though the host may have been detected as inactive earlier by the ReplicaSetMonitor. In this case, we may want to select another secondary host instead of reusing the potentially bad connection. see DBCRS::checkLastHost(). |
| Comments |
| Comment by Andy Schwerin [ 27/Oct/16 ] |
|
No reported user issues related, and we're hoping to remove DBClientReplicaSet, so not going to fix this behavior. |