NODE-7859Backlog

RTTPinger never reschedules after a failed ping, leaving latestRtt frozen at a stale value

h3. Use Case h3. Expected Behavior After a mongos restart, the latency measurement on a server connection should be updated at regular intervals as it was before the restart. h3. Actual Behavior and Impact During a rolling mongos restart, a server node enters quiesce mode and answers the RTT pinger's hello with {{{}ShutdownInProgress{}}}. {{{}RTTPinger.measureRoundTripTime{}}}'s onrejected callback destroys the connection, sets it to undefined, and returns without setting another {{me

Affected Versions
Versions known to exhibit this issue
7.6.0
Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue
SDAM
Labels
Tags and classification
external-usernode-internal