[DOCS-15346] [Server] Investigate changes in SERVER-66495: Aggregations should be counted as Query ops, not Command ops Created: 17/May/22  Updated: 13/Nov/23  Resolved: 21/Sep/23

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Joseph Dougherty
Resolution: Fixed Votes: 0
Labels: query
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-66495 Aggregations should be counted as Que... Closed
Participants:
Days since reply: 23 weeks, 5 days ago

 Description   
Original Downstream Change Summary

If the query team were to make this change, it would change a longstanding meaning in the server status counters and would potentially affect how downstream teams do their tracking. If this would negatively affect a downstream team, please comment on SERVER-66495 or reach out to the query team in #query-execution.

Description of Linked Ticket

Currently, only the official Find Command increments the "Query" OpCounter from db/stats/counters.h. Any use of the aggregation pipeline command is only counted as a "Command", lumped together with all other operations that aren't Query, writes, or getmores.
Since it would be more useful to have all commands that perform query-like operations be counted as queries, we should start counting aggregations as queries.
(Note that we already count get-mores issued on cursors sourced either by aggregation or by finds, without distinction.)



 Comments   
Comment by Jonathan Balsano [ 25/Aug/23 ]

dave.cuthbert@mongodb.com I just want to follow up on this ticket to make sure it doesn't get lost ahead of 7.1.0 given this work has landed. This will impact Cloud as well so having it in the upgrade notes would be helpful! cc frank.sun@mongodb.com

Comment by Dave Cuthbert (Inactive) [ 17/May/22 ]

Sounds like the target version and epic could change. Leaving at 6.0 for now

Comment by Kyle Suarez [ 17/May/22 ]

Docs Team, right now the Query Team has not yet decided to actually implement SERVER-66495, so there is nothing to do right now. But if we were to decide to implement that ticket, then a documentation change would be needed.

Generated at Thu Feb 08 08:12:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.