[SERVER-32307] Make AsyncResultsMerger kill sequence issue killCursors without waiting for outstanding batches Created: 13/Dec/17  Updated: 30/Oct/23  Resolved: 23/Jan/18

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Querying, Sharding
Affects Version/s: None
Fix Version/s: 3.7.2

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Ian Boros
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on SERVER-21710 Allow pinned ClientCursors to be kill... Closed
is depended on by SERVER-24978 Second batches in aggregation framewo... Closed
is depended on by SERVER-28090 Add ability to interrupt operations u... Closed
Duplicate
is duplicated by SERVER-17696 Terminate sharded queries immediately... Closed
Related
related to SERVER-6496 provide a way to kill a sharded query... Closed
related to SERVER-4984 make it possible to interrupt operati... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2018-01-29
Participants:

 Description   

Currently, when a killCursors command is issued against a cursor that is in use (e.g. is pinned and executing a getMore), the cursor will not be cleaned up. In order to accommodate this, the AsyncResultsMerger must delay issuing killCursors commands until all of the outstanding batch requests have been received.

However, we plan to change killCursors to clean up pinned cursors under SERVER-21710. Once this work is complete, AsyncResultsMerger::kill() can schedule killCursors to run against all remote cursors without delay. Once these requests have been scheduled, the AsyncResultsMerger itself can be promptly deleted.



 Comments   
Comment by Githook User [ 23/Jan/18 ]

Author:

{'name': 'Ian Boros', 'email': 'ian.boros@10gen.com'}

Message: SERVER-32307 Change ARM to kill its cursors unconditionally
Branch: master
https://github.com/mongodb/mongo/commit/97341c4326a29b6633edec7e50c051d1c9cf8854

Comment by Ian Whalen (Inactive) [ 29/Dec/17 ]

ian.boros you should pull this forward if you finish everything else in Query 2018-01-15.

Generated at Thu Feb 08 04:29:51 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.