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

Improve the mechanism that collects cache usage stats for the history store

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • 8

      We are currently collecting cache usage information for history store while in __evict_update_work() because the history store dhandle isn't always available to eviction. This is not an ideal way to collect stats as the cached version of stats is used elsewhere by eviction for making decisions and using an outdated version of cache usage can lead to subtle and hard to debug issues.

      The purpose of this ticket is to explore and implement a more robust method to acquire history store cache stats whenever required. This can involve resolving issues around directly accessing underlying history store btree to acquire latest cache usage data (hint: __wt_get_hs_btree()).

      Acceptance criteria:

      • All WT tests are passing after the change
      • Test the changes against the MongoDB reproducer script from WT-6924 and ensure that overall cache usage remains below configured cache size.

            Assignee:
            backlog-server-storage-engines [DO NOT USE] Backlog - Storage Engines Team
            Reporter:
            haseeb.bokhari@mongodb.com Haseeb Bokhari (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated: