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

depends on

SERVER-36299Implement support for exhaust cursors with OP_MSG in DBClientCursor