Mark shardsvrDropCollectionParticipant as non-deprioritizable

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • Catalog and Routing
    • CAR Team 2026-03-16
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This command is used under the critical section in multiple DDL operations and does enough disk accesses (primarily for range deletions) that it may be deprioritized (though somewhat unlikely). We should mark it non-deprioritizable to be safe. Ideally this should affect local calls as well as the participant command.

            Assignee:
            Anna Maria Nestorov
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: