-
Type: Improvement
-
Resolution: Fixed
-
Priority: Major - P3
-
Affects Version/s: None
-
Component/s: Shell
-
Minor Change
-
75
There are several limitations with db.currentOp(), including the documented 16MB result set size. There have been various testing issues because of this, such as SERVER-47513 where the command gets truncated due to the size of the response.
- is related to
-
SERVER-51463 currentOp command silently fails to apply match conditions when result is truncated
- Backlog
-
MONGOSH-1132 Make db.currentOp() use an aggregation stage if possible
- Closed
-
SERVER-55174 Investigate test failure in sharded_collections_causally_consistent_jscore_txns_passthrough suite with db.currentOp change
- Closed
-
SERVER-55175 Maintain original read concern for $currentOp in passthrough suites that change read concern
- Closed
- related to
-
SERVER-55603 Shell read preference behavior is wrong for currentOp
- Closed