Add stats to diagnose cache stuck scenarios

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • WT12.0.0
    • Affects Version/s: None
    • Component/s: Cache and Eviction
    • None
    • Storage Engines, Storage Engines - Transactions
    • SE Transactions - 2026-02-13
    • 3

      In disagg mode, standby crashes frequently due to cache stuck issues.
      There are stats to track the movement of oldest timestamp, stable timestamp and pinned timestamp. But there is no granular visibility of their relevance to cache management.
      This ticket will add the stats to track the values of global timestamps that will influence the cache management.
      The stats will track the values of the global timestamps.
      1) pinned timestamp
      2) oldest timestamp
      3) stable timestamp
      4)oldest txn timestamp
      5) version cursor pinned timestamp

            Assignee:
            Vamsi Boyapati
            Reporter:
            Vamsi Boyapati
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: