[SERVER-32957] Remove notion of "zombie cursors" on mongos Created: 29/Jan/18 Updated: 29/Oct/23 Resolved: 26/Feb/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.7.3 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Ian Boros | Assignee: | Ian Boros |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Query 2018-02-12, Query 2018-02-26, Query 2018-03-12 |
| Participants: |
| Description |
|
Now that we've changed the ARM's kill() to not wait for outstanding batches, there should no longer be a need for "zombie cursors" or a "zombie cursor reaper" in mongos. Note that we'll need to preserve "kill pending" cursors, for the case when killCursors is run an operation in the middle of a getMore. The operation will be interrupted, and until the cursor is checked back in (or out), the it will be marked as "kill pending." |
| Comments |
| Comment by Githook User [ 26/Feb/18 ] |
|
Author: {'email': 'ian.boros@10gen.com', 'name': 'Ian Boros'}Message: |
| Comment by Githook User [ 20/Feb/18 ] |
|
Author: {'email': 'ian.boros@10gen.com', 'name': 'Ian Boros'}Message: |