[SERVER-45230] RTT and isMaster from initial handshake should populate initial ServerDescription record Created: 18/Dec/19 Updated: 08/Jan/24 Resolved: 05/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Lamont Nelson | Assignee: | Janna Golden |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Backport Requested: |
v4.4
|
||||||||||||
| Sprint: | Service Arch 2020-01-13, Service Arch 2020-02-24, Service Arch 2020-03-09 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
The initial handshake of a server connection contains the first isMaster response and associated RTT for a server. Right now this is done here, but the results of the isMaster response and RTT are not accessible outside of this class.
We need to be able to create the initial ServerDescription for a server from the isMaster response and RTT from this initial handshake. This ensures that a server that is added to the topology is always potentially available to be included in server selection.
Note that after this initial handshake the RTT for a server will be updated from the "ServerMonitor" component being developed in
The relevant part of the spec is here. Implementation plan: |
| Comments |
| Comment by Githook User [ 29/Mar/20 ] |
|
Author: {'name': 'jannaerin', 'username': 'jannaerin', 'email': 'golden.janna@gmail.com'}Message: (cherry picked from commit b74fd5ae11cb95a42cf18e996e81136546cfddda) |
| Comment by Githook User [ 04/Mar/20 ] |
|
Author: {'username': 'jannaerin', 'name': 'jannaerin', 'email': 'golden.janna@gmail.com'}Message: |