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

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-10-03

      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.

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

              Created:
              Updated:
              Resolved: