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

Add checks and statistics around the truncate API

    • Type: Icon: Improvement Improvement
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • WT11.0.0, 6.1.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • Labels:
    • 5
    • Storage - Ra 2022-06-13

      Summary
      We want to ensure the records are no longer present after truncated has been executed. This could be done in debug mode only through WT_ASSERT.

      It would also be great to add statistics to know how many records are truncated.

      This will help better diagnose issues related to the truncate API.

      Motivation

      • Does this affect any team outside of WT?
        No
      • How likely is it that this use case or problem will occur?
        Every time truncate is executed
      • Is this issue urgent?
        Yes, we have issues that are hard to diagnose that involve the truncate API.

      Acceptance Criteria (Definition of Done)

      • Testing
        The existing tests might be enough. Just check the stats are generated and the WT_ASSERT is not getting fired.
      • Documentation update
        No

            Assignee:
            monica.ng@mongodb.com Monica Ng
            Reporter:
            etienne.petrel@mongodb.com Etienne Petrel
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: