[SERVER-31044] clone drop-pending collections during initial sync Created: 11/Sep/17 Updated: 27/Oct/23 Resolved: 09/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Assigned Teams: |
Replication
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Since we don't clone them, if we roll back the collection drop, the rollback will fail. This leads to an fassert during rollback, not data corruption. When fixed, we need to make sure that we register the drop pending collection with the reaper so that it gets reaped at the appropriate optime. |