Review Fast Truncate transaction visibility correctness

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Engines - Foundations
    • None
    • 5

      Problem
      The ASC Fast Truncate implementation does not work on standby nodes because it needs to write fast truncate information directly to the standby table which violates the core principle in which any update/insert operations can’t be done in standby mode. A new standby fast truncate design will be adopted to enable fast truncate.

      After WT-15207 has been merged in, a simple POC truncate list will be present in the develop branch. The POC truncate needs to be reviewed to ensure it follows transaction visibility correctness.

      What needs to be done
      The ticket will focus on reviewing if the POC truncate structure properly respects WT transaction and timestamp visibility. Furthermore, python tests and unit tests will be created to validate the transaction visibility correctness.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Jie Chen
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: