[SERVER-66495] Aggregations should be counted as Query ops, not Command ops - MongoDB Jira

XML

Word

Printable

JSON

Details

Type: Improvement
Status: Backlog
Priority: Major - P3
Resolution: Unresolved
Affects Version/s: None
Fix Version/s: None
Component/s: None
Labels:
- RDY
- neweng

Assigned Teams:

Query Execution
Sprint:
QE 2023-02-06, QE 2023-02-20, QE 2023-03-06, QE 2023-03-20, QE 2023-04-03

Description

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.)

Attachments

Issue Links

is depended on by

TOOLS-3121 Investigate changes in SERVER-66495: Aggregations should be counted as Query ops, not Command ops

Closed

TOOLS-3135 Investigate changes in SERVER-66495: Aggregations should be counted as Query ops, not Command ops

Closed

is documented by

DOCS-15346 [Server] Investigate changes in SERVER-66495: Aggregations should be counted as Query ops, not Command ops

Backlog

related to

SERVER-71281 opcounters.command on mongos counts insert, update and delete but opcounters.command on mongod doesn't

Closed

Activity

People

Assignee:: Backlog - Query Execution

Reporter:: Eric Milkie

Participants:: Asya Kamsky, Backlog - Query Execution, Bruce Lucas, Eric Milkie, Kevin Arhelger, Kyle Suarez, Rushan Chen

Votes:: 0 Vote for this issue

Watchers:: 14 Start watching this issue

Dates

Created:: May 16 2022 05:15:47 PM UTC

Updated:: Mar 17 2023 08:00:10 PM UTC