Loading...

XML

Word

Printable

JSON

Type: Task
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 3.7.2
Affects Version/s: None
Component/s: Aggregation Framework, Querying, Sharding
Labels:
None

Backwards Compatibility:
Fully Compatible
Sprint:
Query 2018-01-29

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.

depends on

SERVER-21710 Allow pinned ClientCursors to be killed on mongod

Closed

is depended on by

SERVER-24978 Second batches in aggregation framework are asked synchronously

Closed

SERVER-28090 Add ability to interrupt operations using pinned cursors on mongos

Closed

is duplicated by

SERVER-17696 Terminate sharded queries immediately after a failure

Closed

related to

SERVER-6496 provide a way to kill a sharded query on all shards

Closed

SERVER-4984 make it possible to interrupt operations in mongos

Closed

(1 related to)

Assignee:: Ian Boros

Reporter:: David Storch

Participants:: David Storch, Githook User, Ian Boros, Ian Whalen

Votes:: 0 Vote for this issue

Watchers:: 4 Start watching this issue

Created:: Dec 13 2017 06:59:21 PM UTC

Updated:: Oct 30 2023 11:09:57 PM UTC

Resolved:: Jan 23 2018 03:53:50 PM UTC

Details

Description

Attachments

Issue Links

Activity

People

Dates