-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
v4.0
-
Repl 2018-08-13, Repl 2018-08-27
-
68
If you lose your sync source once you're up to date but before you update your lastOpCommitted, it can prevent secondary majority reads from progressing.
This definitely needs to be investigated for how to do this correctly and safely.
- is related to
-
SERVER-39497 Revert SERVER-33248
- Closed
-
SERVER-32166 Do not clear sync source when going from RECOVERING to SECONDARY
- Closed
- related to
-
SERVER-34855 Blacklist restart_catalog.js from causal consistency suites
- Closed
-
SERVER-39367 lastOpCommitted being reset on restart can cause sync source cycle
- Closed
-
SERVER-40193 Do not propagate commit point through heartbeats when FCV=4.0
- Closed
-
SERVER-40194 Revert SERVER-33248 on 4.0
- Closed