Don't count waits for concurrent placement-version work toward the authoritative collection recovery retry cap

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • ALL
    • CAR Team 2026-06-08
    • 0
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      _recoverCollectionMetadataFromDisk can tassert with "Exhausted maximum number (100) of authoritative collection metadata recovery attempts ..." on hot namespaces under concurrent DDL, even though the system is making forward progress.

      Fix
      Bound only consecutive attempts where this thread had to throw away its own work, not iterations spent waiting on another thread's in-flight progress.
       
       

            Assignee:
            Pol Pinol
            Reporter:
            Pol Pinol
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: