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

ExceededTimeLimit (50) is reported in situations unrelated to maxTimeMS

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 4.0.1, 4.1.2
    • Querying
    • None
    • Minor Change
    • v4.0, v3.6, v3.4
    • Query 2018-07-30
    • 22

    Description

      The original drivers specification for maxTimeMS required that:

      In languages that have exceptions, drivers will declare a new exception type ExecutionTimeout. This new exception is raised when the driver detects the server error code 50 in the server's response to a query, getMore, or command.

      However, since then error code 50 (ExceededTimeLimit) has been re-used by the server to report errors unrelated to maxTimeMS.  This confuses application authors when they receive an ExecutionTimeout exception when they haven't specified maxTimeMS.

      I'm not sure it's possible, but it would be beneficial to users if the server stopped using error code 50 for anything but maxTimeMS-related timeouts.

      Attachments

        Issue Links

          Activity

            People

              james.wahlin@mongodb.com James Wahlin
              jeff.yemin@mongodb.com Jeffrey Yemin
              Votes:
              0 Vote for this issue
              Watchers:
              13 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: