Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-7699

Fix RTS handling to abort an out of order prepared transaction

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.1, 4.4.7, 5.0.0-rc5, 5.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • 3
    • Storage - Ra 2021-06-28
    • v5.0, v4.4

      RTS process has a check to verify the restored update timestamp from the history store must be less than the on-disk version of the data store which is getting replaced due to either it is unstable according to the stable timestamp or a prepared update.

      WT_ASSERT(session, hs_tw->start_ts <= unpack->tw.start_ts); 
      

      This condition can wrong if a prepared update is written to disk and it has an out-of-order prepare timestamp compared to the committed update.

            Assignee:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Reporter:
            haribabu.kommi@mongodb.com Haribabu Kommi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: