-
Type: Improvement
-
Resolution: Unresolved
-
Priority: Major - P3
-
None
-
Affects Version/s: None
-
Component/s: None
-
Query Integration
slow query logs say how long a specific getMore takes, but not how long the entire query took and time between getMores. It would be great to be able to track long running queries in some way.
Specifically for the CA, we were trying to calculate the blast radius for cursors alive for more than 15 minutes, for queries with equality on the shard key.
- related to
-
SERVER-78071 A targeted query with a concurrent yield and chunk migration can miss results
- Backlog