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

Multikey write during recovery of prepared transaction could use commit timestamp < stable timestamp

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.9.0, 4.2.13, 4.4.5
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Backport Requested:
      v4.4, v4.2
    • Sprint:
      Repl 2021-01-25, Repl 2021-02-08
    • Linked BF Score:
      10

      Description

      SERVER-42251 added code of using the prepareTimestamp to timestamp the multi-key write when reconstructing prepared transactions. SERVER-49949 did a fix to use max(prepareTS, oldestTS). But WT doesn't allow writing with timestamp < stable timestamp. And in the case when both the prepareTS and the oldest are < the stable timestamp, e.g. after rollback, we could violate the WT rule. To fix this, I think we should use max(prepareTS, stableTS).

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              lingzhi.deng Lingzhi Deng
              Reporter:
              lingzhi.deng Lingzhi Deng
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: