[SERVER-78028] Add random failures to initial syncs in initial sync concurrency suites Created: 13/Jun/23  Updated: 13/Jul/23

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

Type: Engineering Test Priority: Major - P3
Reporter: Jack Mulrow Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 0
Labels: former-quick-wins
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-76991 Create a "kitchen sink" suite Open
Assigned Teams:
Replication
Participants:

 Description   

We have several concurrency suites that initial sync nodes in the background while fsm workloads run (like concurrency_sharded_initial_sync). If we injected random failures into the initial syncs that required restarting them, we could get more coverage for starting servers with partially synced data.



 Comments   
Comment by Jack Mulrow [ 27/Jun/23 ]

vishnu.kaushik@mongodb.com, yeah the bug in SERVER-78000 required the initial syncing node to restart partway through an initial sync, which c) should trigger, so your understanding sounds right to me.

Comment by Vishnu Kaushik [ 21/Jun/23 ]

jack.mulrow@mongodb.com, I think the suite you linked already performs failovers along with initial sync. However, I took a look at a run from one of my patch builds, and it looks like we make the initial sync node failover but only after it has already transitioned to SECONDARY, and I guess that isn't sufficient to produce the bug you linked.

I guess what we want is to have a) non-initial sync node failovers b) sync source failovers c) initial sync node failover during initial sync. Does that sound right?

Generated at Thu Feb 08 06:37:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.