Remove lock timeout and retry loop in shard catalog timeseries upgrade/downgrade

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.3.0-rc0
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2026-03-30, CAR Team 2026-04-13
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      When we implemented viewless timeseries upgrade/downgrade in SERVER-114505, when acquiring the locks over the view+buckets namespaces, we added a 30s lock timeout and retry loop. This was motivated because some DDLs did not acquire the view+buckets locks in canonical order (increasing ResourceId) so we wanted to preclude deadlocks.

       

      Since SERVER-116090 timeseries DDLs acquire locks for in canonical order like all other operations.

      Furthermore, the lock checker (SERVER-99150) is not flagging any lock ordering violation in all of the upgrade/downgrade suites.

       

      Therefore it's safe to remove the retry loop & lock timeout.

            Assignee:
            Joan Bruguera Micó
            Reporter:
            Joan Bruguera Micó
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: