When the ReplicaSetMonitor detects a new member in a shard, it will update the ShardRegistry to contain the new member. However, a reload on the ShardRegistry can happen before the update gets propagated to the config servers. When this happens, the reload will not contain the new member, and this can cause the ShardRegistry to temporarily "forget" about the new member until the next reload after the config server gets updated with the new member.