-
Type: Bug
-
Resolution: Works as Designed
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
-
ALL
-
- start a fresh mongod
- wait a bit, let the queries against config collection run automatically
- run $queryStats
{ key: { queryShape: { cmdNs: { db: 'config', coll: 'transactions' }, command: 'find', filter: { lastWriteDate: { '$lt': '?date' } }, projection: { _id: true }, sort: { _id: 1 } }, readConcern: {}, collectionType: 'nonExistent' }, metrics: { lastExecutionMicros: Long("186"), execCount: Long("4"), totalExecMicros: { sum: Long("2513"), max: Long("1957"), min: Long("181"), sumOfSquares: Long("3932927") }, firstResponseExecMicros: { sum: Long("2513"), max: Long("1957"), min: Long("181"), sumOfSquares: Long("3932927") }, docsReturned: { sum: Long("0"), max: Long("0"), min: Long("0"), sumOfSquares: Long("0") }, firstSeenTimestamp: ISODate("2023-09-14T12:30:09.483Z"), latestSeenTimestamp: ISODate("2023-09-14T12:45:09.478Z") }, asOf: Timestamp({ t: 1694695781, i: 0 }) }
Unsure if this is a bug or not, but this doesn't seem like a "nonexistent" collection. maybe "collection" or "virtual"
- is depended on by
-
SERVER-85096 TRACKING: M3 Correctness Tickets
- Closed