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

Log BucketId on a time-series direct write

    • Type: Icon: Task Task
    • Resolution: Won't Do
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • v8.0
    • Execution Team 2024-07-22

      If buckets are manually modified using direct writes, corrupting them in an always compressed world can be easy. This will make the data integrity check fire the next time the BucketCatalog tries to use this bucket. By logging the BucketId we can have some history to see that the bucket was manually modified to get an idea of how the corruption was introduced.

       

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

              Created:
              Updated:
              Resolved: