-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
Repl 2020-02-24
-
0
-
None
-
None
-
None
-
None
-
None
-
None
-
None
In test OplogFetcherAutoReconnectsButFails, the intention was to simulate a disconnect while the oplog fetcher is waiting for a response from the first find command and shut down the remote server before the oplog fetcher retries to connect. However, if _mockServer->shutdown() runs too fast, it could fail the initial connection as well, which is not what this test was intended for.
Instead, we should use simulateNetworkDisconnect to simulate a disconnect then use the hangBeforeOplogFetcherRetries failpoint to hang the retry and shut down the remote server before the oplog fetcher retries.