[SERVER-15602] Add (cppunit) test for initial sync + sync delay behavior Created: 10/Oct/14  Updated: 06/Dec/22  Resolved: 04/May/18

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

Type: Improvement Priority: Minor - P4
Reporter: Scott Hernandez (Inactive) Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: datarepl3.2
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-18038 DataReplicator Applier: Storage Inter... Closed
depends on SERVER-18039 Add Initial Sync Skeleton to DataRepl... Closed
Related
related to SERVER-34828 initial sync should not consider slav... Closed
Assigned Teams:
Replication
Participants:

 Description   

We had a flaky jstest which attempted to test something like this but did so in a non-deterministic way which has recently been removed (~2.7.7). The goal of this issues is to synchronize the initial sync with writes and ensure that that replica gets the writes which happened during the initial sync period until it transition to slave-delay aware and that no docs are lost/delayed exceptionally.

Old test: slaveDelay2.js



 Comments   
Comment by Benety Goh [ 04/May/18 ]

Slave delay is not part of the initial sync oplog application logic as of SERVER-34828

Generated at Thu Feb 08 03:38:28 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.