[SERVER-49475] Investigate adding an option to shrink the oplog at startup Created: 13/Jul/20 Updated: 02/Aug/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Storage Execution
|
| Backwards Compatibility: | Fully Compatible |
| Participants: |
| Description |
|
When a user finds themselves in an out-of-disk-space situation, recovering can be tricky: data can only be removed after startup is complete, but without provisioning extra storage, startup will likely again fail due to disk full as a result of replaying the oplog for recovery purposes. Investigate whether shrinking the oplog at startup, potentially in combination with restarting as standalone and running compact on the oplog, would actually help users and would be worthwhile in terms of development cost. |
| Comments |
| Comment by Cris Insignares Cuello [ 10/Oct/22 ] |
|
michael.gargiulo@mongodb.com Do you have any update about the priority of this ticket? |
| Comment by Connie Chen [ 18/Apr/22 ] |
|
michael.gargiulo@mongodb.com to see if he can find the related HELP ticket |