Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-75740

system.profile collection is created using untimestamped writes but dropped using timestamped writes

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 7.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2023-04-17, Execution Team 2023-05-01, Execution Team 2023-05-15, Execution Team 2023-05-29
    • 135

      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.

            Assignee:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Reporter:
            gregory.wlodarek@mongodb.com Gregory Wlodarek
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: