Investigate if HS record remains after dropping a file

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: History Store, Verify
    • None
    • Storage Engines, Storage Engines - Persistence
    • SE Persistence - 2025-12-05
    • None

      I'd like to investigate a scenario that could lead to an issue:

      • verify() checks the HS and verifies there is a DS record for each HS entry
      • If the DS does not contain any record, verify should fail with:
        the associated history store key <some_key> was not found in the data store <some_file>
        
      • I believe that in the case of a drop, the HS records associated with the file are not immediately removed. If we trigger verify(), we should be able to hit the error

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: