Remove history store records for table drop in step-up case

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

      This comes as a consequence of WT-15800.  When a table is dropped, we normally want to truncate the history store for that table. However on a follower, our changes for WT-15800 remove any shared history store truncation to avoid the HS being modified and being mistakenly written when closed.

      However, if the follower steps up, it will retain the history store info for the dropped table.  Either we need to revisit our solution for WT-15800 or have some sort of HS cleanup.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Donald Anderson
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: