Expand CollectionsInUse to get hit when entering a writeConflictRetry loop

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Fixed
    • Priority: Major - P3
    • 8.3.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2025-12-08, CAR Team 2025-12-22
    • 2
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      SERVER-90992 introduced a collection misuse detector in debug builds. However, this gets hit after the fact and it's a bit of a pain to detect where this is happening.

      A scenario we've seen in SERVER-94613 is entering a writeConflictRetry loop with a lock-free collection acquisition. In that case we can trigger a WT snapshot abandonment that would lead to a stale pointer being held.

      To prevent this we should add a debug check when entering the WCR loop. This will hopefully detect more dangerous scenarios.

            Assignee:
            Jordi Olivares Provencio
            Reporter:
            Jordi Olivares Provencio
            Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated:
              Resolved: