[SERVER-15166] Cursors should never be timed-out but should be closed at disconnection Created: 08/Sep/14 Updated: 24/Dec/19 Resolved: 24/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Networking, Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | PHO | Assignee: | DO NOT USE - Backlog - Platform Team |
| Resolution: | Done | Votes: | 2 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
The current behavior of cursors regarding timeouts has these three problems:
So I propose these changes:
|
| Comments |
| Comment by Spencer Jackson [ 24/Dec/19 ] |
|
Logical sessions does solve most of this request, and I believe changes to the authorization system makes it possible to kill your own cursors resolving the rest. |
| Comment by Shane Harvey [ 07/Dec/18 ] |
These two problems have been fixed by the introduction of sessions in MongoDB 3.6 server and drivers. You can now write client side code that keeps a cursors alive as long as you want and the server will automatically clean up the cursor 30 minutes after the client crashes. See |