[SERVER-38123] Add a "cursor touch" call that would reset the cursor timeout without fetching the next document Created: 14/Nov/18 Updated: 06/Dec/22 Resolved: 19/Nov/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | William Byrne III | Assignee: | Backlog - Query Team (Inactive) |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Query
|
||||||||
| Participants: | |||||||||
| Case: | (copied to CRM) | ||||||||
| Description |
|
Using cursor.noCursorTimeout() to set it to never expire is only useful as a testing setting. In a production environment, there needs to be some way to keep the cursor open under sometimes indeterminate levels of load, especially if the system relies on event queues. What is needed is a way to reset the cursor timeout without fetching the next document, similar to the Unix touch command that changes a file's access and modification times without actually editing the file. |
| Comments |
| Comment by David Storch [ 19/Nov/18 ] |
|
Closing as a duplicate of |
| Comment by William Byrne III [ 18/Nov/18 ] |
|
david.storch - confirmed |
| Comment by David Storch [ 16/Nov/18 ] |
|
william.byrne, I believe this is a duplicate of |