[SERVER-37451] Move all cursor ownership to the global cursor manager Created: 03/Oct/18  Updated: 29/Oct/23  Resolved: 15/Jan/19

Status: Closed
Project: Core Server
Component/s: Querying
Affects Version/s: None
Fix Version/s: 4.1.7

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

Issue Links:
Problem/Incident
Related
related to SERVER-38722 CollectionCloner should handle QueryP... Closed
related to SERVER-3964 Dropping an index invalidates all cur... Closed
Backwards Compatibility: Fully Compatible
Sprint: Query 2018-12-03, Query 2018-12-17, Query 2018-12-31, Query 2019-01-14, Query 2019-01-28
Participants:
Linked BF Score: 0

 Description   

Code deletion is saved as later work; this is just the behavioral change to stop using the per-collection CursorManager instances. This also involves changing PlanExecutor to advertise its lock policy, so that callers no longer need to rely on whether the cursor is globally managed in order to decide whether to acquire locks.



 Comments   
Comment by Githook User [ 17/Jan/19 ]

Author:

{'username': 'dstorch', 'email': 'david.storch@10gen.com', 'name': 'David Storch'}

Message: SERVER-37451 Unblacklist background_unique_indexes.js from initial sync passthrough.
Branch: master
https://github.com/mongodb/mongo/commit/2eab0e010d383c974cd51eaf7ee61144e0c8ccfe

Comment by Githook User [ 15/Jan/19 ]

Author:

{'username': 'dstorch', 'email': 'david.storch@10gen.com', 'name': 'David Storch'}

Message: SERVER-37451 Move all ClientCursor ownership to the global CursorManager.

Deleting the per-collection CursorManagers, and other
related cleanup, is left as future work.
Branch: master
https://github.com/mongodb/mongo/commit/de2a803ca492261cac1d7f43a9f7c847cd0ea24d

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