[SERVER-44014] Add missing synchronization points to initial sync fuzzer Created: 15/Oct/19  Updated: 29/Oct/23  Resolved: 12/Nov/19

Status: Closed
Project: Core Server
Component/s: Replication, Testing Infrastructure
Affects Version/s: None
Fix Version/s: 4.3.1

Type: Improvement Priority: Major - P3
Reporter: Judah Schvimer Assignee: Samyukta Lanka
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Tested
is testing SERVER-43875 Initial sync may crash due to missing... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2019-11-18
Participants:

 Description   

SERVER-43875 wasn't caught by the initial sync fuzzer since it doesn't have "synchronization" points before and between the "start fetch" and "start apply" remote commands. We should add synchronization points there like we do explicitly during oplog application so the fuzzer runs commands in between those steps. I don't think this requires any fuzzer changes, but it will likely require changes to the initial sync test fixture test.



 Comments   
Comment by Samyukta Lanka [ 12/Nov/19 ]

Accidentally committed this with a typo in the ticket name, so here's a link to the commit in github.

Author:

{'username': 'lankas', 'email': 'samy.lanka@mongodb.com', 'name': 'Samyukta Lanka'}

Message: SERVER=44014 Add missing synchronization points to initial sync fuzzer
Branch: master
https://github.com/mongodb/mongo/commit/e13eebf4a091b3725e35312114684518fb7afde5

Comment by Robert Guo (Inactive) [ 21/Oct/19 ]

Thanks Judah. I agree Repl would be a better position to do this.

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