-
Type: Task
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
When the shell makes a query against a replica set, the query stats key included the `$readPreference` field even if it's not explicitly included in the command (according to slow query logs). This doesn't happen in the standalone or sharded cluster cases. We want to minimize differences in query stats from different kinds of deployment, so ideally this wouldn't happen.
- is related to
-
SERVER-88520 $queryStats' readConcern has a default value on mongos only
- Backlog