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

Avoid/Suppress mixed_mode write on config.transactions

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.1.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • 6

    Description

      When writing to config.transaction documents, we make an optimization to only write the latest value. This can happen for vectored inserts on a primary or after an batch of oplog application. However, after rolling back, we're expected to have the appropriate version of config.transactions documents as of the stable timestamp. Because the storage engine may never have been told about the document, we fix this by synthesizing the right version and persisting it without a timestamp. That update violates the ordered constraint.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: