-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.0, v3.6, v3.4
-
Repl 2018-07-02, Repl 2018-07-16
-
(copied to CRM)
We added retry logic into the OplogFetcher in SERVER-25702 to increase robustness of initial sync. By doing so, however, we also added these restarts into regular steady state replication. This can slow down sync source resolution unnecessarily when one node is unavailable but other nodes would be able to serve as the sync source.
- duplicates
-
SERVER-32703 Secondary can take a couple minutes to re-establish sync source after network partition
- Closed
- is duplicated by
-
SERVER-35835 Allow quicker sync source change when a new Primary is elected
- Closed
- is related to
-
SERVER-42910 Oplog query with higher timestamp but lower term than the sync source shouldn't time out due to afterClusterTime
- Closed
-
SERVER-35996 Create performance tests for measuring failover speed for planned stepdowns
- Closed
- related to
-
SERVER-25702 add support to OplogFetcher for restarting oplog query
- Closed
-
SERVER-32703 Secondary can take a couple minutes to re-establish sync source after network partition
- Closed
-
SERVER-35835 Allow quicker sync source change when a new Primary is elected
- Closed