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

Applying a rename operation can result in multiple WT transactions

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor - P4
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1, 4.2.4
    • Component/s: Storage
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.2
    • Sprint:
      Execution Team 2019-08-26

      Description

      When renaming a collection via an oplog entry, it's possible to hit this clause. That statement performs work in its own WUOW/transaction and commits separately to completing the rename.

      Note this logic is not a bug in the sense that it would only manifest if crashing/restarting during initial sync were smarter than retrying from the beginning.

      However, this splitting of transactions results in an untimestamped write on the catalog. Verifying that all (necessary) writes to the catalog are timestamped is easier if that's also true during initial sync. The motivation for this ticket is to add timestamp verification.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              daniel.gottlieb Daniel Gottlieb
              Reporter:
              daniel.gottlieb Daniel Gottlieb
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: