-
Type:
Task
-
Resolution: Fixed
-
Priority:
Major - P3
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
Fully Compatible
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
At the moment the releaseMemory command locks everything that getMore would lock. Some of those locks are not necessary for the releaseMemory command since it does not access the collection, it only works with a stage's local state. We should look into how the locking before the command can be minimised to only what the command needs (i.e., lock the TRS)
- blocks
-
SERVER-105926 If releaseMemory fails with an unexpected error, we should destroy the cursor
-
- Closed
-
- is related to
-
SERVER-105787 Interrupting releaseMemory should not interrupt the cursors
-
- Closed
-