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

          depends on

          Improvement - An improvement or enhancement to an existing feature or task. WT-9201 change mixed-mode to a per-transaction basis

          • Major - P3 - Major loss of function.
          • Closed
          has to be done before

          Technical Debt - WT-9276 remove support for mixed-mode

          • Minor - P4 - Minor loss of function, or other problem where easy workaround is present.
          • Closed
          is duplicated by

          Task - A task that needs to be done. SERVER-66253 Remove cases of write_timestamp_usage=mixed_mode

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

          Bug - A problem which impairs or prevents the functions of the product. SERVER-68330 [6.0] Allow mixed_mode writes on config.transactions

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

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: