also assume this can happen in other related mongos node checks.

This causes strange behavior when a replica set is temporarily detected as down because the primary has broken connections - if operations are occurring while the ReplicaSetMonitorWatcher is refreshing the view of the replica set, the node is marked as "ok" and the old primary is assumed to be the current primary for a short period of time.