Provide a way to mark internal, remote commands as non-deprioritizable

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Catalog and Routing
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For 8.3, we marked remote commands as non-deprioritizable by identifying them on the recipient. This is not very maintainable and also is prone to false positives. Instead, we should provide a way to mark an operation as non-deprioritizable at the command level via some generic argument which is internal only (similar to mayBypassUserWriteBlocking).

      We should also consider making this generic such that any priority/task type can be specified. This would allow us to replace the existing exemptions for the oplog fetcher with this new mechanism as well.

            Assignee:
            Unassigned
            Reporter:
            Allison Easton
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: