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

Substitute ghost timestamp with no-op write in multi-statement txn multikey sidetxn write

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.4.0-rc7, 4.7.0
    • Replication, Storage
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Repl 2020-05-18
    • 50

    Description

      SERVER-41766 changed the catalog multikey update for multi-statement transactions on primaries to happen in a side transaction. This side transaction looks at the logical clock to find a timestamp far enough in the future to use for writing to the catalog.

      Because (I believe) we only perform this ghost timestamp on primaries, it's preferable to instead write a no-op oplog entry. That way the stable timestamp never races with the transaction being committed. Durable history may have different consequences due to these races.

      Attachments

        Issue Links

          Activity

            People

              judah.schvimer@mongodb.com Judah Schvimer
              daniel.gottlieb@mongodb.com Daniel Gottlieb
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: