[SERVER-21895] Prevent creating capped collections larger than disk Created: 14/Dec/15 Updated: 06/Dec/22 Resolved: 19/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication, Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Osmar Olivo | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Participants: | |||||||||
| Description |
|
Today there are no guard rails on creation of capped collection. It's possible to ask for a capped collection to be created that is larger then the volume itself. This causes issues in use cases that create new collections automatically, or if you fail to account for the index sizes when gauging the size of a capped collection. This can lead to failure and periods of unavailability (possibly downtime). |
| Comments |
| Comment by Eric Milkie [ 19/Feb/19 ] |
|
Since WiredTiger does not pre-allocate capped collections to their max size, this ticket effectively has gone away. |