[SERVER-29468] Add jstest(s) using renameCollection that fail with current rollback algorithm Created: 06/Jun/17  Updated: 30/Oct/23  Resolved: 19/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Allison Chang Assignee: Allison Chang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-06-19, Repl 2017-07-10
Participants:

 Description   

We want to write tests that we expect will fail with the current rollback algorithm. Specifically, we know that renameCollection can cause the corruption of data during rollback and would like to write tests in order to show this problem. Once we have implemented using UUID's (Universally Unique IDentifier) in non-WT rollback, these tests can be used to confirm that rollback occurs successfully without data corruption.



 Comments   
Comment by Githook User [ 19/Jun/17 ]

Author:

{u'username': u'archang68', u'name': u'Allison Chang', u'email': u'allison.chang@10gen.com'}

Message: SERVER-29468 Add jstest to check for data corruption after rolling back renameCollection op
Branch: master
https://github.com/mongodb/mongo/commit/41adaa028c9c088179b53a1b4ac5c4fe59725d04

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