[SERVER-32899] Add background index builds and multikey index writes to rollback fuzzer Created: 25/Jan/18  Updated: 06/Dec/22  Resolved: 29/May/18

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Backlog - Replication Team
Resolution: Won't Fix Votes: 0
Labels: rollback-optional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-31799 Run rollback fuzzer with upgrades Closed
Assigned Teams:
Replication
Sprint: Repl 2018-02-26, Repl 2018-03-12
Participants:

 Description   

These are edge cases we've discovered in our implementation, adding them to the fuzzer could expose bugs.



 Comments   
Comment by Spencer Brody (Inactive) [ 29/May/18 ]

We will get some coverage of multi-key writes within transactions being rolled back as part of the work on SERVER-33863.

This ticket would cover adding multi-key writes outside of transactions, and background index builds (which we wait to complete before starting rollback).  But we think the value of testing those scenarios is relatively low.

Comment by Judah Schvimer [ 26/Jan/18 ]

Per conversation with robert.guo, the rollback fuzzer already does background index builds, but since there is only one client, those essentially are foregrounded on the primary. ( See https://docs.mongodb.com/v3.6/core/index-creation/#behavior). We should add the ability to run multiple clients, or at least one off parallel shells for background index builds, to the fuzzer. This could be used by SERVER-31799 to run setFCV commands at different points during rollback (since those will block on majority writes).

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