-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Execution
-
None
-
3
-
None
-
None
-
None
-
None
-
None
-
None
Currently when we merge on router and have $mergeCursors stage, it doesn't respect batch size and reads the whole shard output in a single call, leaving nothing a releaseMemory command to do.
We should work around it to allow release command tests for sharding.