[SERVER-40194] Revert SERVER-33248 on 4.0 Created: 18/Mar/19  Updated: 29/Oct/23  Resolved: 22/Mar/19

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.8

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: Tess Avitabile (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-39367 lastOpCommitted being reset on restar... Closed
is related to SERVER-40193 Do not propagate commit point through... Closed
is related to SERVER-33248 Allow choosing a sync source that we ... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-03-25, Repl 2019-04-08
Participants:

 Description   

SERVER-33248 allows a node to choose a sync source with the same lastApplied if it has a higher lastOpCommitted. This leads to sync source cycles, as described in SERVER-39367. This is fixed on 4.2 in SERVER-39367, which reverts the change while introducing a new mechanism to propagate the majority commit point through heartbeats. However, SERVER-39367 is not safe to backport to 4.0, since it increases the likelihood of sync source cycles with nodes that have SERVER-33248. On 4.0, we will just revert SERVER-33248.


Generated at Thu Feb 08 04:54:18 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.