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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.2.0-rc5, 4.3.1
    • Affects Version/s: 4.2.0-rc2
    • Component/s: Replication
    • None
    • Fully Compatible
    • ALL
    • v4.2
    • Repl 2019-07-29
    • 19
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Will Schultz
              Reporter:
              Will Schultz
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: