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

Test that DBClientCursor sends getMore for exhaust cursor if moreToCome is not set

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.0.3
    • Component/s: Replication
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Repl 2018-08-27, Repl 2018-09-10

      Description

      It is legal in the spec for exhaust cursors for the server to not set the moreToCome bit when the cursor is not exhausted. In this case, the client should send a getMore in order to receive more results. We should test that DBClientCursor adheres to this spec by creating a failpoint that randomly does not set the moreToCome bit and checking that DBClientCursor sends a getMore to get the next batch.

        Attachments

          Issue Links

            Activity

              People

              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: