Everywhere that uses the RemoteCommandTargeter to talk to replica sets for PrimaryOnly operations needs to be prepared to receive a NotMaster response. Currently DBClientReplicaSet feeds information back into the ReplicaSetMonitor when it receives NotMaster responses so the monitor knows to refresh its view of the who the current primary is. We need to duplicate this logic when using the RemoteCommandTargeter.
- is related to
-
SERVER-19404 Ensure that all places using RemoteCommandTargeter to run PrimaryOnly commands have NotMaster retry logic
- Closed