[SERVER-84000] Investigate magic restore maintenance process Created: 07/Dec/23 Updated: 08/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Ali Mir | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Replication
|
| Participants: |
| Description |
|
After magic restore is complete, we'll need to lay out the best way to maintain it going forward. If an change is introduced in MongoDB that breaks the magic restore process, we'll need to add any new steps to the magic restore logic and update any relevant documentation. We should figure out whether this will fall to replication or the implementer of the breaking change with a repl reviewer, and codify the process in some form of documentation. |