-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
None
-
Query Integration
-
ALL
-
None
-
None
-
None
-
None
-
None
-
None
-
None
The solution for the data race issue SERVER-108789 is less than ideal because the operation memory usage tracker stays attached to the Exchange object, and so is never attached to a cursor. When using $currentOp to see memory in use by idle cursors, this memory will never be reported.
We should come up with a way to address this.
- is related to
-
SERVER-108789 Fix data race when multiple exchange cursors access OperationMemoryUsageTracker
-
- Closed
-
- related to
-
SERVER-110499 Allow tracking memory for stages after Exchange
-
- Backlog
-
-
SERVER-109511 Implement memory tracking for exchange stage buffered documents
-
- Backlog
-