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

Find and getMore commands should use a default timeout of 1 second for tailable, awaitData cursors

XMLWordPrintableJSON

    • Type: Icon: Task Task
    • Resolution: Done
    • Priority: Icon: Major - P3 Major - P3
    • 3.1.7
    • Affects Version/s: None
    • Component/s: Querying
    • None
    • Fully Compatible
    • Quint Iteration 7

      Currently, when you issue a getMore on a tailable, awaitData cursor, the client must supply a maxTimeMS value. This maxTimeMS is used as the timeout while blocking and waiting for more data. If not supplied, the server will fail the query.

      Instead, the server should use a default timeout of 1 second if maxTimeMS is not supplied on the getMore.

            Assignee:
            qingyang.chen Qingyang Chen
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: