[SERVER-84357] Exclude the oplog when auto compaction is enabled by default Created: 20/Dec/23 Updated: 10/Jan/24 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Etienne Petrel | Assignee: | Backlog - Storage Engines Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Assigned Teams: |
Storage Engines
|
||||||||||||
| Sprint: | StorEng - Refinement Pipeline, 2024-01-09 - I Grew Tired | ||||||||||||
| Participants: | |||||||||||||
| Story Points: | 3 | ||||||||||||
| Description |
|
We should exclude the oplog as well when background compaction is enabled through gEnableAutoCompaction. This ticket should ensure the oplog is excluded whether background compaction is enabled through the autoCompact command or gEnableAutoCompaction. Furthermore, we should avoid duplicating code. If possible, we should create a function that would definite the collections that are excluded by default. |
| Comments |
| Comment by Etienne Petrel [ 09/Jan/24 ] | |
|
With the following test:
I found that in notifyStartupComplete, both LocalOplogInfo::get(opCtx) Question:
cc'ing you gregory.wlodarek@mongodb.com as you may have more context regarding background compaction and what we added in notifyStartupComplete. | |
| Comment by Etienne Petrel [ 08/Jan/24 ] | |
|
louis.williams@mongodb.com, I have also noticed the field _oplogRecordStore, would it be ok to use this one instead of what you suggested? |