[SERVER-29691] Two Phase Drops: implement database drop rollback logic Created: 16/Jun/17  Updated: 30/Oct/23  Resolved: 28/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Benety Goh Assignee: Judah Schvimer
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-29470 Create new files for rollback code fo... Closed
Duplicate
is duplicated by SERVER-28208 Recoverable Rollback: Support rolling... Closed
is duplicated by SERVER-20984 Support rolling back database drops Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2017-07-10
Participants:
Case:

 Description   

As specified in the 2-phase drop design, to rollback a database drop, we would simply create an empty database since all collection drops in a database drop cannot be rolled back. The reason for this is that we would wait for the collection drops to be replicated to a majority of the nodes in a replica set before writing out the oplog entry for the database drop.



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

Author:

{u'username': u'judahschvimer', u'name': u'Judah Schvimer', u'email': u'judah@mongodb.com'}

Message: SERVER-29691 rolls back dropDatabase commands
Branch: master
https://github.com/mongodb/mongo/commit/4d3756aca8409150628e8c62712f6ca10616d2cb

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