[SERVER-61763] Add query related metrics to serverStatus & currentOp Created: 29/Nov/21  Updated: 12/Aug/22  Resolved: 12/Aug/22

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-68803 Add whether SBE is in use to currentO... Closed
Sprint: Execution Team 2022-01-24, Execution Team 2022-06-27, Execution Team 2022-08-22
Participants:

 Description   

Project task placeholder.



 Comments   
Comment by Dianna Hohensee (Inactive) [ 12/Aug/22 ]

I've filed SERVER-68806 to look into generally setting the read timestamp on currentOp, whenever we have one. And I've filed SERVER-68803 with query to generally put a flag on currentOp when a SBE query is running.

I don't think there's anything further that would be useful to add, that I can currently think of. Resolving.

Comment by Dianna Hohensee (Inactive) [ 12/Aug/22 ]

I realize that a lot of read concerns aren't going to specify a timestamp at which to read, in which case this won't be helpful.

Comment by Dianna Hohensee (Inactive) [ 11/Aug/22 ]

I made a pass through the design document suggestions/proposals for metrics. What we do not yet track, and still seem worthwhile adds, are the following:

CurrentOp additions:

  • Track the current snapshot read timestamp in use.
  • Track whether or not the ClientCursor’s cursors are positioned across yield.
  • IdleCursors
    • Read timestamp, if cursors are positioned
Generated at Thu Feb 08 05:53:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.