Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-21005

Consistent maxTimeMs / timeout / interruption support

    XMLWordPrintableJSON

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Duplicate
    • None
    • None
    • Internal Code
    • Sharding 2019-02-25

    Description

      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).

      Attachments

        Issue Links

          is duplicated by

          New Feature - A new feature of the product, which has yet to be developed. SERVER-35679 General Interruption Facility

          • Major - P3 - Major loss of function.
          • Closed
          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-23625 Some read-only operations (eg count,aggregate) hang indefinitely if the primary for the shard is unreachable from mongos

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              blake.oler@mongodb.com Blake Oler
              schwerin@mongodb.com Andy Schwerin
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: