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

change_stream_enforce_max_time_ms_on_mongos.js expects getMore to schedule follow-up getMores

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 3.6.8, 4.0.1, 4.1.1
    • Component/s: Aggregation Framework
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v4.0, v3.6
    • Sprint:
      Query 2018-07-02
    • Linked BF Score:
      26

      Description

      The test issues a getMore with a maxTimeMS of 500, and expects this command to schedule getMores on each of the shards. After SERVER-34204 this is no longer the case, since the subsequent getMores may be delayed until the next getMore comes in.

      We should re-write the test to account for this possibility, or we should add a unit test for this behavior and delete the assertions from the javascript test.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              david.storch David Storch
              Reporter:
              charlie.swanson Charlie Swanson
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: