[SERVER-44679] Rollback fuzzer must account for transactions that may not have been rolled back. Created: 15/Nov/19  Updated: 06/Jan/20  Resolved: 06/Jan/20

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

Type: Bug Priority: Major - P3
Reporter: Matthew Russotto Assignee: Pavithra Vetriselvan
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Duplicate
duplicates SERVER-37390 RollbackTestFixture doesn't need to w... Closed
Related
related to SERVER-37390 RollbackTestFixture doesn't need to w... Closed
related to SERVER-42650 Remove stale comments mentioned in th... Closed
Operating System: ALL
Sprint: Repl 2019-12-16, Repl 2019-12-30, Repl 2020-01-13
Participants:
Linked BF Score: 6

 Description   

We already take into account that some rollbacks may not occur during rollback shutdown tests

https://github.com/mongodb/mongo/blob/103318868c860e441050652b6dae137d0d21d593/jstests/replsets/libs/rollback_test.js#L215

However, we don't take into account that these rollbacks that don't happen may include prepared transactions, which prevent us from doing data consistency checks. In rollback tests with shutdowns we must account for rolled-back prepared transactions possibly still being around, and abort them explicitly or skip consistency checks.



 Comments   
Comment by Pavithra Vetriselvan [ 06/Jan/20 ]

After SERVER-37390, we actually ensure that rollback won't be skipped during shutdowns by waiting until the new primary oplog entry that's written in the new term gets persisted to disk. Closing this ticket as a Duplicate.

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