[SERVER-75740] system.profile collection is created using untimestamped writes but dropped using timestamped writes Created: 05/Apr/23 Updated: 29/Oct/23 Resolved: 22/May/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Gregory Wlodarek |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | techdebt | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Execution Team 2023-04-17, Execution Team 2023-05-01, Execution Team 2023-05-15, Execution Team 2023-05-29 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 135 | ||||||||
| Description |
|
When enabling profiling on a database, the system.profile collection is created using an untimestamped write to the catalog. But when running dropDatabase, the system.profile collection is dropped using a timestamped write to the catalog. This mixed-mode usage makes it difficult to reason in the CollectionCatalog. It will simplify the CollectionCatalog if both the create/drop are either timestamped or untimestamped, not mixed. |
| Comments |
| Comment by Githook User [ 22/May/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |