Provide a general way for ShardingCoordinator's to mark their opCtx non-deprioritizable within the critical section

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 9.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • Fully Compatible
    • CAR Team 2026-03-30, CAR Team 2026-04-13
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Similar to what was done under SERVER-121287, we should make it such that all opCtx created by coordinators are marked as non-depriortizable within the critical section. The sharding coordinator already has a specialized makeOperationContext helper which sets forwardable op metadata on it, so we can extend this to also conditionally set the non-deprioritizable state.

      One possible approach here would be to update the makeOpertionContext helper to take in a Phase. Then, for each coordinator we can have a function which returns whether or not a phase is in the critical section. This can then be used to decide whether or not to mark the new opCtx non-deprioritizable.

            Assignee:
            Wolfee Farkas
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: