[SERVER-44939] Allow data replication across config versions Created: 04/Dec/19  Updated: 29/Oct/23  Resolved: 30/Jan/20

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

Type: Task Priority: Major - P3
Reporter: Siyuan Zhou Assignee: Pavithra Vetriselvan
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Duplicate
is duplicated by SERVER-45083 Allow data replication across config ... Closed
Related
related to SERVER-47097 Add isPrimary to ReplSetMetadata and ... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.2
Sprint: Repl 2020-01-27, Repl 2020-02-10
Participants:
Case:

 Description   

Safe Reconfig requires data replication across config versions for liveness reasons.

Currently, we do not sync from a node that has a different config version. The oplog fetcher checks if it should stop fetching from the sync source (after it has fetched the first batch).

shouldStopFetching calls replCoord->shouldChangeSyncSource which finally calls topCoord->shouldChangeSyncSource. Here, we check for the various reasons we would want to change sync source (i.e. not being in the same config).



 Comments   
Comment by Githook User [ 30/Jan/20 ]

Author:

{'username': 'pvselvan', 'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}

Message: SERVER-44939 allow replication across config versions
Branch: master
https://github.com/mongodb/mongo/commit/101eb1694568df1ff086a460cc6c511eacc05860

Generated at Thu Feb 08 05:07:25 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.