[SERVER-28206] Recoverable Rollback: Support rolling back of dropCollection oplog entries using collection UUIDs. Created: 06/Mar/17 Updated: 06/Dec/22 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: | Backlog - Replication Team |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Participants: | |||||||||
| Description |
|
The existing rollback implementation in 3.4 requires the entire collection to be copied from the sync source when rolling back a dropCollections command. With the introduction of Collection UUIDs in 3.6 and 2-phase drops in 3.6, this should no longer be necessary. We can recover the dropped collection by fixing up the Namespace to UUID links in the collection catalog. |
| Comments |
| Comment by Allison Chang [ 03/Aug/17 ] |
|
Completed in |