SERVER-139348Needs Scheduling

replSetGetStatus reports pingMs=0 for members that have a priorityPort configured

h3. Summary When a replica set member has {{members[].priorityPort}} set (and {{disableReplicationUsageOfPriorityPort}} is false), {{replSetGetStatus}} always reports {{members[].pingMs: 0}} for that member. The heartbeat RTT is recorded, but under a different key than the one {{replSetGetStatus}} reads. h3. Cause * Heartbeats are sent to {{getHostAndPortPriority()}} ({{replication_coordinator_impl_heartbeat.cpp}}, {{auto target = rsc.getMemberAt(i).getHostAndPortPriority();}}). The ping stats

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix

No fix available yet.

Components
Server components related to this issue

No components specified.

Labels
Tags and classification

No labels assigned.