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

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Fixed
    • Priority: Major - P3
    • 4.0.3
    • Affects Version/s: None
    • Component/s: Replication
    • None
    • Fully Compatible
    • Repl 2018-08-27, Repl 2018-09-10
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      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.

            Assignee:
            Will Schultz
            Reporter:
            Tess Avitabile (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: