[SERVER-46885] Allow "refreshing" cursors as we can do with sessions Created: 16/Mar/20 Updated: 19/Mar/20 Resolved: 19/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor - P4 |
| Reporter: | Remi Jolin | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
When running large batch that iterate over a cursor and each step takes long time, we often need to increase the cursorTimeoutMillis parameters (here we use the equivalent of 2 hours and we still have "unknown cursor" errors sometime). With sessions we have the ability to refresh them (db.refreshSessions(sessions_ids_list)) so we can deal with long sessions that would normally expire. Don't you thing it would be intersting to get the same refresh mechanism at the cursor level ? db.refreshCursors(cursors_ids_list) |
| Comments |
| Comment by Carl Champain (Inactive) [ 19/Mar/20 ] |
|
I'm going to close this ticket as a duplicate of Thank you, |
| Comment by Remi Jolin [ 19/Mar/20 ] |
|
dmitry.agranat Yes, it seems to look like what I'd like. |
| Comment by Dmitry Agranat [ 19/Mar/20 ] |
|
Hi rj-10gen@arsynet.com, could you please review |
| Comment by Remi Jolin [ 17/Mar/20 ] |
|
This could help solving issue described here Of course it would refresh all the "sub-cursors" in each shard. |