[SERVER-27305] Create integration tests that do rollbacks with potentially problematic sequences of operations Created: 06/Dec/16  Updated: 02/Oct/17  Resolved: 02/Oct/17

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: William Schultz (Inactive)
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-31130 Add javascript test to exercise simpl... Closed
Related
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-10-02, Repl 2017-10-23
Participants:

 Description   

(updated description)
This will be implemented in C++ as an end-to-end unit test for the new rollback algorithm.

------

Various commands, especially collection metadata commands, can cause rollback failures if they occur in the right order on the rolling-back node or the node's sync source. We should create a suite of tests for the known problematic operation sequences and another suite that runs random operations on both the rollback node and its sync source to catch unknown problematic scenarios.

The random test should log all operations it runs for maximum debuggability. Both should include a consistency check at the end.



 Comments   
Comment by Gregory McKeon (Inactive) [ 02/Oct/17 ]

judah.schvimer should this be closed as a duplicate?

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