[SERVER-21750] getMore command does not set "nreturned" operation counter Created: 02/Dec/15 Updated: 16/Nov/16 Resolved: 11/Dec/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.1, 3.3.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | code-and-test | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Completed: | |||||||||||||||||
| Sprint: | QuInt D (12/14/15) | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
The "nreturned" field is never displayed in the diagnostic log line generated by the getMore command. "nreturned" is properly shown for legacy OP_GET_MORE requests. Reproduce with the following script:
Output from the server when "commands" read mode is forced ("nreturned" not present for getMore):
Output from the server when "legacy" read mode is forced ("nreturned" present for getMore):
|
| Comments |
| Comment by Githook User [ 11/Dec/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: --Omit ntoreturn and ntoskip from the getMore command log line. (cherry picked from commit bb7e1e539da115da4ee1146c79e47c23109dce95) |
| Comment by Githook User [ 11/Dec/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: --Omit ntoreturn and ntoskip from the getMore command log line. |
| Comment by David Storch [ 04/Dec/15 ] |
|
We should also consider including keysExamined and docsExamined in the getMore command log lines (and maybe planSummary). We may also want to suppress ntoreturn and ntoskip, as we did for the find command log lines. |