[DOCS-6962] Update Rollback Limitations (300 MB limit) to cover only updates, deletes and not inserts Created: 12/Jan/16 Updated: 30/Oct/23 Resolved: 01/Nov/22 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | manual, Server |
| Affects Version/s: | None |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Scott Hernandez (Inactive) | Assignee: | Unassigned |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | bite-sized | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Location: https://docs.mongodb.org/manual/core/replica-set-rollbacks/#rollback-limitations |
||
| Participants: | |
| Days since reply: | 1 year, 14 weeks, 1 day ago |
| Epic Link: | DOCSP-1769 |
| Story Points: | 0.25 |
| Description |
|
The limitations part referring to 300MB of data refers to the data which needs to be retrieved from the upstream source (like updates or deleted docs which must be rolled back) not any inserted docs (which will be saved to the rollback files) which must be removed during the rollback. For a largely insert workload this may result in very large rollback files. |
| Comments |
| Comment by Education Bot [ 01/Nov/22 ] |
|
Hello! This ticket has been closed due to inactivity. If you believe this ticket is still important, please reopen it and leave a comment to explain why. Thank you! |