Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.5.10
Affects Version/s: None
Component/s: Replication
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Repl 2017-07-10
Case:
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Judah Schvimer
Reporter:: Benety Goh
Participants:: Benety Goh, Githook User, Judah Schvimer
Votes:: 0 Vote for this issue
Watchers:: 3 Start watching this issue

Created:: Jun 16 2017 06:05:27 PM UTC
Updated:: Oct 30 2023 11:15:58 PM UTC
Resolved:: Jun 28 2017 03:49:29 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates