[SERVER-47135] Guarantee that a ServerDescription with ServerType not Unknown has an RTT Created: 26/Mar/20 Updated: 29/Oct/23 Resolved: 16/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Haley Connelly | Assignee: | Backlog - Service Architecture |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Service Arch
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
Goal: We want to be able to establish that when there is a ServerDescription that is not unknown, that it has an rtt. When an isMaster comes in after the initial handshake, there is no currentRtt by design, and there is no guarantee that there is a lastRtt if the ServerDescription is not Unknown. We would like to ensure ReplicaSetMonitorManager::validateHost is called after dropConnections before any new connections are established. |
| Comments |
| Comment by Lamont Nelson [ 16/Apr/20 ] |
|
This invariant is established by the handshake validation code here: https://github.com/mongodb/mongo/blob/master/src/mongo/client/replica_set_monitor_manager.cpp#L92 |