[SERVER-29959] Fix renameCollection step in rollback via refetch Created: 03/Jul/17  Updated: 30/Oct/23  Resolved: 31/Jul/17

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

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

Issue Links:
Depends
depends on SERVER-30150 Two Phase Drops: rolling back cross d... Closed
is depended on by SERVER-18310 Can't rollback dropCollection if new ... Closed
Duplicate
is duplicated by SERVER-28207 Recoverable Rollback: Support rolling... Closed
Related
is related to SERVER-30212 Use two phase drop for renameCollecti... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-07-31, Repl 2017-08-21
Participants:

 Description   

Currently in the 3.4 FCV of rollback, we handle rolling back renameCollection commands by resyncing the entire collection, which is inefficient and can lead to data corruption. In 3.6, with the implementation of UUIDs, we want to avoid full collection resyncs and fix the problem with data corruption after collections are renamed.



 Comments   
Comment by Githook User [ 31/Jul/17 ]

Author:

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

Message: SERVER-29959 Update rollback of renameCollection commands to use UUIDs
Branch: master
https://github.com/mongodb/mongo/commit/6b34ad314773be3f3214d6f4186fde6ec0c12e39

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