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

The `captrunc` test command doesn't atomically delete data and indexes

    • Type: Icon: Bug Bug
    • Resolution: Won't Fix
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Storage
    • None
    • Storage Execution
    • ALL
    • Execution Team 2022-10-17, Execution Team 2022-10-31

      The captrunc test command invokes cappedTruncateAfter without a WUOW. Based on the implementation of WiredTigerRecordStore::doCappedTruncateAfter, this means that first the indexes will be detached for the deleted records and later on, the actual data will get truncated in a separate WUOW.

      This means if a crash happens in between the two, the index and data will remain inconsistent.

      Without a crash of the server, there is not a problem because the whole command runs with a collection X-lock.

            Assignee:
            backlog-server-execution [DO NOT USE] Backlog - Storage Execution Team
            Reporter:
            kaloian.manassiev@mongodb.com Kaloian Manassiev
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: