SERVER-13244Open
Secondary that enters RECOVERY mode does not reset connections
When a node changes state normally (most notably from an election) it disconnects all sockets partly to ensure the change of state is noticed. However, when a Secondary enters RECOVERY mode due to a compact command, it does not close existing sockets. Clients using secondaryPreferred continue to utilize the node as a normal secondary (operations either get blocked or return a failure due to "not primary or secondary") but new clients do not attempt to issue queries because the invalid state is