[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: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Sprint: | Repl 2017-07-10 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| 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: |