Consistent maxTimeMs / timeout / interruption support

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Duplicate
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Internal Code
    • Sharding 2019-02-25
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      While maxTimeMs is for providing soft deadlines for operations, the server could do a much better job adhering to those deadlines and better support interruption without major architectural changes. The purpose of this project is to make maxTimeMs deadline-oriented, and to improve its behavior when operations involve several nodes communicating (as in sharding).

            Assignee:
            Blake Oler
            Reporter:
            Andy Schwerin
            Votes:
            0 Vote for this issue
            Watchers:
            10 Start watching this issue

              Created:
              Updated:
              Resolved: