SERVER-133198ClosedFixed

Handle stale primary member data case in sync source selection

In SERVER-96495, we [added logic|https://github.com/mongodb/mongo/blob/6efa48969872ee9a29ed082b26e63c83ab6a6fe6/src/mongo/db/repl/topology_coordinator.cpp#L395-L429] to prefer syncing from the primary if we are choosing between the primary and another node in a datacenter. The check is done using [member data of each node|https://github.com/mongodb/mongo/blob/6efa48969872ee9a29ed082b26e63c83ab6a6fe6/src/mongo/db/repl/topology_coordinator.cpp#L395-L396]. However, this data may be stale, since

Affected Versions
Versions known to exhibit this issue

No affected versions recorded.

Fixed Versions
Versions that include the fix
9.1.0-rc09.0.48.3.168.0.37
Components
Server components related to this issue
Replication
Labels
Tags and classification
bkp