[SERVER-33091] Create rollback tests that do all types of catalog writes while nodes are both in primary and secondary state Created: 02/Feb/18  Updated: 29/Oct/23  Resolved: 16/May/18

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

Type: Task Priority: Major - P3
Reporter: Judah Schvimer Assignee: Kyle Suarez
Resolution: Fixed Votes: 0
Labels: rollback-non-functional
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-35002 Replace RollbackTest with RollbackTes... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-04-23, Repl 2018-05-07, Repl 2018-05-21
Participants:

 Description   

How catalog writes are timestamped is often different for writes that occur while a node is primary vs. secondary. Most of our rollback tests do not make this distinction. We should make some deterministic tests that exercise this behavior and also ensure that the rollback fuzzer is exercising it. We should make the writes occur on both sides of the common point. Getting operations applied as a secondary that have to be rolled back will likely require a 5 node replica set with a double rollback.



 Comments   
Comment by Githook User [ 16/May/18 ]

Author:

{'email': 'kyle.suarez@mongodb.com', 'username': 'ksuarz', 'name': 'Kyle Suarez'}

Message: SERVER-33091 create a rollback test with 5 nodes

This test suite allows for a controlled rollback where nodes roll back
writes performed as a primary or secondary.
Branch: master
https://github.com/mongodb/mongo/commit/5c722f8e8eea601f37519678b7458dc95befe28d

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