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

XMLWordPrintableJSON

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

      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
              Reporter:
              Daniel Gottlieb (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: