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

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.9.0, 4.2.13, 4.4.5
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • v4.4, v4.2
    • Repl 2021-01-25, Repl 2021-02-08
    • 10
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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).

            Assignee:
            Lingzhi Deng
            Reporter:
            Lingzhi Deng
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: