ExportXMLWordPrintableJSON

    • Storage Engines - Transactions
    • 62.869
    • None
    • None

      WT-18807 identified that cache accounting inconsistencies are currently reported as ERROR messages by __wt_cache_destroy, but the function still returns success. This is intentional historical behavior and was not changed as part of the diagnostics-only work in WT-18807.

      Investigate whether a normal close with leak_memory=false should return an error when cache/page/image/scrub accounting is non-zero.

      Acceptance criteria:

      • Define the desired WT_CONNECTION.close contract for non-zero cache accounting.
      • Determine the appropriate error code and behavior during final teardown.
      • Consider existing WT_CONN_CLOSE_ABORT diagnostics and application compatibility.
      • Add focused test coverage for the chosen behavior.
      • Preserve the explicitly supported leak_memory=true shutdown behavior, or define and test its exception separately.

      Related: WT-18807.

            Assignee:
            [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            Chenhao Qu
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: