Details
-
Improvement
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
Query Execution
-
Fully Compatible
-
QE 2023-05-15, QE 2023-05-29, QE 2023-06-12, QE 2023-06-26, QE 2023-08-07
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
-
- Closed
-
- related to
-
SERVER-71281 opcounters.command on mongos counts insert, update and delete but opcounters.command on mongod doesn't
-
- Closed
-
-
SERVER-79297 Count and distinct should be counted as Query ops, not Command ops
-
- Backlog
-