-
Type: Bug
-
Resolution: Done
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
Fully Compatible
-
ALL
-
v4.0
-
Repl 2018-05-07, Repl 2018-05-21, Repl 2018-06-04
-
27
Currently a transient network error during rollback can result in the secondary fasserting. We should retry all network operations during rollback at least once or twice so we can avoid shutting down the server unless absolutely necessary.
- is depended on by
-
SERVER-21051 Add a suite that runs existing sharding tests while probabilistically dropping messages within the CSRS
- Closed
- is related to
-
SERVER-35004 Add functionality to only fail specific command(s) in failCommand failpoint
- Closed
- related to
-
SERVER-20711 Fatal assertion in secondary when sync failed due to network problems
- Closed