[SERVER-21086] mongos does not kill cursor with getMore command when batch size gets you exactly to the limit Created: 23/Oct/15 Updated: 06/Dec/22 Resolved: 02/Aug/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying, Sharding |
| Affects Version/s: | 3.2.0-rc0 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Jeffrey Yemin | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 1 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Query
|
||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The getMore command should not return a cursor id if the limit specified on the find command has been satisfied by the returned batch. But if the batch size specified on the getMore command gets you just to the limit, then a cursor id is still returned by mongos. A subsequent getMore will correctly return an empty batch and no cursor id. This does not happen with mongod. |
| Comments |
| Comment by David Storch [ 02/Aug/19 ] |
|
This appears to be a slightly different manifestation of SERVER-19915. Closing as a duplicate. |