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

Correctly timestamp catalog writes for index recovery when an oplog entry timestamp is present

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.2.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-10-03

    Description

      We use canAcceptWritesFor to determine if we're a primary which among other things, controls whether we should timestamp writing to the catalog. There are cases where we are writing to the catalog with a perfectly valid timestamp from an oplog entry, but we omit passing the timestamp to the transaction.

      Attachments

        Issue Links

          is depended on by

          Bug - A problem which impairs or prevents the functions of the product. SERVER-60753 Removing index build entries from 'config.system.indexBuilds' can make mixed mode writes

          • Major - P3 - Major loss of function.
          • Closed
          split to

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-69877 Remove untimestamped writes to the catalog when restarting unfinished index builds during startup recovery

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              gregory.wlodarek@mongodb.com Gregory Wlodarek
              daniel.gottlieb@mongodb.com Daniel Gottlieb
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: