While a query is yielded, it may be killed for a number of reasons, including:
- collection drop
- database drop
- index drop
Killed queries that have generated a partial result set will return these partial results without returning an error. We should consider having killed queries fail with a useful error message.
- is depended on by
-
SERVER-18493 Add FSM test interleaving collection/index drop and queries
- Backlog
- is duplicated by
-
SERVER-20973 Initial sync during index drop can cause loss on new member
- Closed
-
SERVER-14752 Btree cursor returns partial result without error if reIndex occurs during yield
- Closed
-
SERVER-11960 Better handling of PlanExecutor::FAILURE in getmore
- Closed
-
SERVER-5169 partial result set rather than assertion in some cases when a cursor is overtaken by a cap point overrun on yield
- Closed
-
SERVER-12689 Improve log message when capped cursor is overrun
- Closed
- related to
-
SERVER-22195 queryoptimizer3.js failing on 2.6
- Closed
-
SERVER-2816 invalidating cursors for one collection may kill cursors for another collection
- Closed
-
SERVER-13123 All callers of PlanExecutor::getNext need to deal with error returns
- Closed
-
SERVER-16920 Better error messages for operations killed during yield
- Closed