[SERVER-31366] profile_getmore.js does not tolerate killCursors command Created: 03/Oct/17 Updated: 30/Oct/23 Resolved: 06/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.4.10, 3.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Backport Requested: |
v3.4
|
||||||||
| Sprint: | Query 2017-10-23 | ||||||||
| Participants: | |||||||||
| Linked BF Score: | 0 | ||||||||
| Description |
|
The profile_getmore.js test creates a cursor and assigns its client-side DBQuery representation to a variable called cursor: It then leaves this cursor open on the server, while the client assigns a second DBQuery object to the cursor variable: The abandoned cursor, however, may now be garbage collected by the shell at any time. When a DBQuery is garbage collected, it issues a killCursors command to the server in order to clean up any server-side state. Therefore, after line 81, a killCursors command may at any arbitrary point during the test's execution be issued against the database under test. The test's assertions are not prepared to handle such a command appearing in the system.profile entry. We must fix the test to either
|
| Comments |
| Comment by Githook User [ 09/Oct/17 ] |
|
Author: {'email': 'david.storch@10gen.com', 'name': 'David Storch', 'username': 'dstorch'}Message: (cherry picked from commit aff9c7e6afe0b78e91a724fe5e53ea4717d7d813) Conflicts: |
| Comment by Githook User [ 06/Oct/17 ] |
|
Author: {'email': 'david.storch@10gen.com', 'name': 'David Storch', 'username': 'dstorch'}Message: |