In the source code we have a check to bypass the shard version check when the primary connection is in the bad state. However, it appears to be incomplete.
The state of the connection will not be recognized as bad until the OS figures it out (e.g. with keepalive), or until we try to use it. Hence it's possible to encounter a scenario when primary is unreachable, but the connection is still recognized as valid, so we will try to check the shard version, which triggers the replicasetrefresh, and we will encounter the 5 sec timeout there on each and every query. Plus we can also get delayed by other threads who are doing the refresh, as it's a serialized action.
If we already know that the primary server is down (i.e. the monitor knows), we probably can avoid checking the shard version if possible.
- is related to
SERVER-16693 It is possible to read unowned data from the primary after fail-over