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

Untimestamped writes to the catalog can occur when dropping unfinished indexes during replication rollback

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
      None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Execution Team 2023-01-23
    • 58

      During replication rollback, all index builds are stopped. When reopening the catalog, any unfinished index builds that weren't secondary background index builds have their index entry in the catalog dropped. This performs an untimestamped write. There's no oplog entry associated with this write, but we can probably use the common point timestamp the node rolled back to.

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

              Created:
              Updated:
              Resolved: