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

Allow RTS to operate when stable timestamp is not set

    • Type: Icon: New Feature New Feature
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT10.0.0, 4.4.2, 4.9.0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 5
    • Storage - Ra 2020-10-05, Storage - Ra 2020-10-19, Storage - Ra 2020-11-02

      In an environment where there are no timestamps are used, to fix the inconsistent checkpoint that may get generated, RTS must operate on data files even when there is no stable timestamp is set.

      As part of PM-1826, the RTS is re-designed to ignore/skip invoking RTS on tables with the following conditions.

      • Empty table.
      • Table has timestamped updates without a stable timestamp.
      • Table where corruption is detected.

      Other tables that do not meet the above conditions will go through the RTS mechanism to rollback any of the updates which are more than the stable timestamp.

        1. RTS_NonTimestamped.diff
          7 kB
        2. WT_6712.diff
          3 kB

            ravi.giri@mongodb.com Ravi Giri
            haribabu.kommi@mongodb.com Haribabu Kommi
            0 Vote for this issue
            6 Start watching this issue