-
Type: Bug
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
ALL
-
v4.0
-
Repl 2019-03-11
-
15
Consider two nodes in a set, nodes A and B. Node A restarts (resetting its lastOpCommitted to 0) and is ahead of node B. Node B syncs from A. A has no lastOpCommitted so A chooses to sync from B which has a non-zero lastOpCommitted, even though B is already syncing from A.
- is duplicated by
-
SERVER-39497 Revert SERVER-33248
- Closed
- is related to
-
SERVER-27123 Only update commit point via spanning tree
- Closed
-
SERVER-39353 disable chaining in rollback_test.js
- Closed
-
SERVER-39497 Revert SERVER-33248
- Closed
-
SERVER-39626 Majority committed oplog entries may be rolled back on minority nodes
- Closed
-
SERVER-39831 Never update commit point beyond last applied if learned from sync source
- Closed
-
SERVER-33248 Allow choosing a sync source that we are up to date with if it has a higher lastOpCommitted
- Closed
- related to
-
SERVER-40193 Do not propagate commit point through heartbeats when FCV=4.0
- Closed
-
SERVER-40194 Revert SERVER-33248 on 4.0
- Closed