[SERVER-31799] Run rollback fuzzer with upgrades Created: 02/Nov/17  Updated: 06/Dec/22  Resolved: 29/May/18

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

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

Issue Links:
Related
related to SERVER-32899 Add background index builds and multi... Closed
related to SERVER-31805 rollbackViaRefetchNoUUID fails if rol... Closed
Assigned Teams:
Replication
Participants:

 Description   

Rollback is allowed to occur during MongoDB major version upgrade (though not downgrade), so it would be great to test it. It should run with the old rollback algorithm, so we may need to blacklist extra operations.



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

This doesn't seem like the highest value testing work we could do now or in the immediate future.

Comment by Judah Schvimer [ 26/Jan/18 ]

This would still be useful with the new rollback algorithm. Majority writes in setFCV will block during parts of rollback, so this will have to be done in a background process at random points throughout rollback.

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