Details
-
Improvement
-
Status: Closed
-
Minor - P4
-
Resolution: Gone away
-
None
-
None
-
None
-
Query 2019-01-28
-
(copied to CRM)
-
4
Description
When you drop an index, we invalidate all open cursors on the collection that that index was on. It would be better if we could detect which cursors are using the index and only invalidate those cursors.
Per SERVER-8975 this occurs even if the index to be dropped does not exist.
Attachments
Issue Links
- is documented by
-
DOCS-12375 Document that in 4.2, an index drop will no longer kill a query which is not using the index
-
- Closed
-
- is duplicated by
-
SERVER-21061 Killing one index build interrupts another one on the same collection
-
- Closed
-
-
SERVER-8975 Deleting non-existent indexes on a collection drops active (basic) cursors on that collection
-
- Closed
-
- is related to
-
DOCS-1236 document cursor lifecycle
-
- Closed
-
-
SERVER-37451 Move all cursor ownership to the global cursor manager
-
- Closed
-
- related to
-
SERVER-13626 dropping an index aborts other bg index builds
-
- Closed
-