[SERVER-40417] Log time spent waiting for mongot Created: 01/Apr/19  Updated: 27/Oct/23  Resolved: 22/May/19

Status: Closed
Project: Core Server
Component/s: Diagnostics, Querying
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: David Storch Assignee: Ted Tuckman
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
is related to SERVER-40416 Log mongot cursor id and time spent b... Closed
Sprint: Query 2019-06-03
Participants:

 Description   

Log slow FTS queries to the log file.

 

The intent of this ticket is to have $_internalFTSMongotRemote include diagnostic log lines for slow queries. These messages will obey the configured slowms, and will only appear if the time spent contacting the mongot exceeds that threshold.

The log messages will include the mongot cursor ID.



 Comments   
Comment by David Storch [ 22/May/19 ]

bruce.lucas, we filed two tickets, but it was simpler for ted.tuckman to implement both pieces of work together. All the implementation work and discussion of the change should happen under SERVER-40416. I'm closing this ticket as "Gone Away", as it won't have any commits against it.

Comment by Bruce Lucas (Inactive) [ 22/May/19 ]

Since this is going to be user-facing can somebody please post the proposed design here for discussion? For example the names used should be consistent with names used elsewhere, e.g. SERVER-31368.

Comment by Evan Nixon [ 02/Apr/19 ]

Hi bruce.lucas - our intention here was "log file", I will flesh out the ticket a bit more to better communicate that!

Comment by Bruce Lucas (Inactive) [ 01/Apr/19 ]

Does this mean log file, serverStatus, currentOp, or all of the above?

Generated at Thu Feb 08 04:54:54 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.