[SERVER-45051] Implement class that collects RTT information from replica set members Created: 10/Dec/19  Updated: 29/Oct/23  Resolved: 07/Feb/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.3.4

Type: New Feature Priority: Major - P3
Reporter: Lamont Nelson Assignee: Haley Connelly
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-45521 Define TopologyListener, ServerPingMo... Closed
Related
related to SERVER-45607 Expose ping times for hosts on the Re... Closed
Backwards Compatibility: Fully Compatible
Sprint: Service Arch 2019-12-16, Service Arch 2019-12-30, Service Arch 2020-01-13, Service Arch 2020-01-27, Service Arch 2020-02-10
Participants:

 Description   

Since the isMaster conversation will be one-way in the normal case, the RSM will use a dedicated connection to issue ping commands to measure round trip latency. The RSM will update the RTT for a server in it's ServerDescription record, according to SDAM.

We'll need a class that can:
1. Allow callers to add/remove servers that need to be pinged.
2. Accept the ping interval as a parameter.
3. Publish RTT values observed for a server.



 Comments   
Comment by Githook User [ 07/Feb/20 ]

Author:

{'username': 'haleyConnelly', 'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com'}

Message: SERVER-45051 Implement class that collects RTT information from replica set members

create mode 100644 src/mongo/client/sdam/topology_listener_mock.cpp
create mode 100644 src/mongo/client/sdam/topology_listener_mock.h
create mode 100644 src/mongo/client/server_ping_monitor_test.cpp
Branch: master
https://github.com/mongodb/mongo/commit/7dedade0d5f44bcfd491116c498e4fbb440c2337

Comment by Haley Connelly [ 13/Jan/20 ]

Split this ticket up into 2 pieces: Defining the skeletons for the classes involved with measuring RTT (SERVER-45521) and implementing the functionality (which will be done in this ticket).

Generated at Thu Feb 08 05:07:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.