[SERVER-36539] Test that DBClientCursor sends getMore for exhaust cursor if moreToCome is not set Created: 08/Aug/18  Updated: 29/Oct/23  Resolved: 28/Aug/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 4.0.3

Type: Task Priority: Major - P3
Reporter: Tess Avitabile (Inactive) Assignee: William Schultz (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-36299 Implement support for exhaust cursors... Closed
Backwards Compatibility: Fully Compatible
Sprint: Repl 2018-08-27, Repl 2018-09-10
Participants:

 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.



 Comments   
Comment by William Schultz (Inactive) [ 28/Aug/18 ]

Included in the unit tests added in SERVER-36299.

Comment by William Schultz (Inactive) [ 28/Aug/18 ]

This should be covered this unit test case.

Generated at Thu Feb 08 04:43:24 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.