[SERVER-22038] changelog and actionlog become non-capped after drop Created: 31/Dec/15 Updated: 06/Dec/22 Resolved: 18/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.0.8, 3.2.0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Kevin Pulo | Assignee: | [DO NOT USE] Backlog - Sharding Team |
| Resolution: | Done | Votes: | 0 |
| Labels: | max-triage | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||
| Assigned Teams: |
Sharding
|
||||||||||
| Operating System: | ALL | ||||||||||
| Steps To Reproduce: |
|
||||||||||
| Participants: | |||||||||||
| Description |
|
config.changelog and config.actionlog are created as 10MB and 2MB capped collections. However, if they are dropped, then the next time a document is inserted they get auto-recreated as regular (non-capped) collections. From there they can expand to consume large amounts of disk space. One solution would be to automatically correct this situation by periodically (eg. each balancer round) checking to see if these collections aren't capped, and if so, running convertToCapped on them. |