-
Type: Task
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Replication
-
None
-
Fully Compatible
-
Repl 2017-07-10
-
(copied to CRM)
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.
- depends on
-
SERVER-29470 Create new files for rollback code for collections without uuid
- Closed
- is duplicated by
-
SERVER-28208 Recoverable Rollback: Support rolling back of dropDatabase oplog entries.
- Closed
-
SERVER-20984 Support rolling back database drops
- Closed