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

Cannot timestamp multikey write during recovery of prepared transaction before LogicalClock has been initialized

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: 4.2.0-rc2
    • Fix Version/s: 4.2.0-rc5, 4.3.1
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.2
    • Sprint:
      Repl 2019-07-29
    • Linked BF Score:
      19

      Description

      When reconstructing a prepared transaction during replication recovery, we try to timestamp a multikey write with a timestamp from the LogicalClock. The LogicalClock may not have been initialized yet, though, which leads to an error if we try to timestamp the write with a zero timestamp. A proposed solution is to instead propagate the prepare timestamp of the transaction into that codepath so that we can timestamp the write with the transaction's prepare timestamp.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              william.schultz William Schultz (Inactive)
              Reporter:
              william.schultz William Schultz (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: