[SERVER-8683] Handle asynchronous cursor destruction from clients Created: 22/Feb/13 Updated: 06/Dec/22 Resolved: 05/Jul/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 2.2.3, 2.4.0-rc0 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Ben Becker | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | query-44-grooming | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Assigned Teams: |
Query
|
| Operating System: | ALL |
| Participants: |
| Description |
|
Issue was discovered because the JavaScript GC can free cursor objects at any time, which sends a killcursor command. This can interfere with GetLastError calls, as can be seen from the following test failures: |
| Comments |
| Comment by David Storch [ 05/Jul/19 ] |
|
This issue pertains to old test failures which have not been seen recently. Also, getLastError is no longer relevant for modern clients which use the write commands. Closing as Gone Away. |
| Comment by Greg Studer [ 22/Feb/13 ] |
|
commit 29ccd88fccfeb88cad4217be482a335ac81a8fb7 make mongos log killCursor requests |
| Comment by auto [ 22/Feb/13 ] |
|
Author: {u'date': u'2013-02-22T21:45:13Z', u'name': u'Ben Becker', u'email': u'ben.becker@10gen.com'}Message: |