Loading...

XML

Word

Printable

JSON

Type: Improvement
Resolution: Fixed
Priority: Major - P3
Fix Version/s: 5.0.0-rc0
Affects Version/s: None
Component/s: Shell
Labels:
- greenerbuild
- qopt-team

Backwards Compatibility:
Minor Change
Linked BF Score:
75
Confidence Status:
None
Work Order:
3
CAR Domain/s:
None

Aha! Reference:
None
Tracking Level:
None
Risk Status:
None
Exec Notes:
None
Goal Name(s):
None
Goal Link:
None

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

Assignee:: Katherine Wu (Inactive)
Reporter:: Nicholas Zolnierz
Participants:: Githook User, Katherine Wu, Nicholas Zolnierz
Votes:: 0 Vote for this issue
Watchers:: 8 Start watching this issue

Created:: Apr 16 2020 06:31:19 PM UTC
Updated:: Oct 29 2023 10:09:23 PM UTC
Resolved:: May 07 2021 07:22:25 PM UTC
Confidence Status Last Update:: 09/Apr/21 1:46 PM

Details

Description

Attachments

Issue Links

Forms

Activity

People

Dates