[SERVER-51102] Use new $currentOp aggregation pipeline stage in count_plan_summary.js Created: 23/Sep/20  Updated: 29/Oct/23  Resolved: 23/Sep/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.8.0

Type: Improvement Priority: Major - P3
Reporter: Tommaso Tocci Assignee: Tommaso Tocci
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
is depended on by SERVER-51074 VectorClock is not gossiped correctly... Closed
Related
is related to SERVER-51463 currentOp command silently fails to a... Backlog
Backwards Compatibility: Fully Compatible
Sprint: Sharding 2020-10-05
Participants:

 Description   

The old currentOp command has a limitation of 16MB maximum response size and could be truncated, giving false negative test results.



 Comments   
Comment by Githook User [ 23/Sep/20 ]

Author:

{'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}

Message: SERVER-51102 Use new $currentOp aggregation pipeline stage in count_plan_summary.js

The old currentOp command has a limitation of 16MB maximum response size and
could be truncated, giving false negative test results.
Branch: master
https://github.com/mongodb/mongo/commit/37a2cc5751829912c56c657b1d906a55039a1a29

Generated at Thu Feb 08 05:24:30 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.