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

Add 'maxAwaitTimeMs' parameter to getMore command, deprecate usage of 'maxTimeMS' with getMore

    XMLWordPrintableJSON

Details

    • Query Execution
    • Minor Change

    Description

      The confusion between the generic 'maxTimeMS' argument used for any command and the specific role it plays in a getMore on a tailable, awaitData cursor leads to some unfortunate complexity in the server. The server needs to remember and special-case this argument for getMores. In those cases, the server needs to avoid setting a deadline on the operation to prevent a "fake" timeout, but remember and parse maxTimeMS as a time limit for how long to wait for new inserts.

      This confusion has lead to many build failures, increased to complexity of development for change streams, and adds some overhead to command processing, although this overhead is probably negligible.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            1 Vote for this issue
            Watchers:
            20 Start watching this issue

            Dates

              Created:
              Updated: