Consolidate stale collection/database exception handling on shards

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Done
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • Sharding EMEA 2022-11-14, Sharding EMEA 2022-11-28
    • 2
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Currently we have duplicated code to handle stale collection/database exceptions:

      This code duplication often lead to confusion and is very error prone (e.g SERVER-68932)

              Assignee:
              Unassigned
              Reporter:
              Tommaso Tocci
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: