[SERVER-24704] Stats for aggregation overcounted in Top Created: 22/Jun/16  Updated: 06/Dec/22  Resolved: 16/Mar/17

Status: Closed
Project: Core Server
Component/s: Aggregation Framework, Diagnostics
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Minor - P4
Reporter: Kevin Albertson Assignee: Backlog - Query Team (Inactive)
Resolution: Duplicate Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Duplicate
duplicates SERVER-22541 Aggregation plan executors should be ... Closed
Assigned Teams:
Query
Operating System: ALL
Steps To Reproduce:

In the shell run

db.toptest.insert({a:1})
db.adminCommand("top")

The entry for toptest should show a command count of 0. Then run

db.toptest.aggregate([{$match: {}}])
db.adminCommand("top")

And now the toptest entry should show a command count of 2.

Participants:

 Description   

Top records some aggregation pipelines as two commands instead of one.



 Comments   
Comment by Charlie Swanson [ 16/Mar/17 ]

This has been resolved by work on SERVER-22541, specifically this commit.

Comment by Ian Whalen (Inactive) [ 05/Dec/16 ]

cc charlie.swanson

Generated at Thu Feb 08 04:07:10 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.