[SERVER-22381] Capped Collection size should account for Data + Index Created: 30/Jan/16 Updated: 06/Dec/22 Resolved: 19/Feb/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Angshuman Bagchi (Inactive) | Assignee: | Backlog - Storage Execution Team |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||
| Operating System: | ALL | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
Currently capped collection size does not account for index size. This can lead to situations where a capped collection fits the volume it is on, but the additional space required by the indexes causes it to exceed the capacity of the volume. See related ticket : |
| Comments |
| Comment by Eric Milkie [ 19/Feb/19 ] |
|
Capped collection enhancements are being phased out in favor of TTL enhancements. The request in this ticket would be very hard to implement in practice. |