[SERVER-28208] Recoverable Rollback: Support rolling back of dropDatabase oplog entries. Created: 06/Mar/17 Updated: 03/Aug/17 Resolved: 03/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Judah Schvimer |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
With 2-phase drops, dropDatabase will no longer require a full resync. Individual dropCollection oplog entries will also be generated for each dropDatabase command so that we can simply process the individual dropCollection oplog entries on rollback and ignore the dropDatabase operation. |