[SERVER-68976] Log time spent waiting for read concern Created: 18/Aug/22  Updated: 05/Dec/22

Status: Backlog
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Dmitry Ryabtsev Assignee: Backlog - Replication Team
Resolution: Unresolved Votes: 10
Labels: former-quick-wins, readconcern
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-18067 Add the time spent waiting for write ... Closed
Assigned Teams:
Replication
Participants:

 Description   

This is a request similar to SERVER-18067.

At present the only way to infer if a query might have waited for read concern is by checking for the lag at the time of query execution. This is not straightforward and can still be inconclusive, especially if the query execution time & lag are under 1 second (i.e. t2 resolution is limited to 1s).

Would be nice to have the time spent by a query waiting for read concern as a separate item in the log message.



 Comments   
Comment by Opal Hoyt [ 22/Aug/22 ]

Recommend doing these at the same time

Generated at Thu Feb 08 06:12:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.