[SERVER-68803] Add whether SBE is in use to currentOp output Created: 12/Aug/22  Updated: 29/Oct/23  Resolved: 15/Nov/22

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

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Alyssa Clark
Resolution: Fixed Votes: 0
Labels: query-offsite
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by COMPASS-6307 Investigate changes in SERVER-68803: ... Closed
is depended on by TOOLS-3220 Investigate changes in SERVER-68803: ... Closed
Documented
is documented by DOCS-15743 Investigate changes in SERVER-68803: ... Closed
Related
related to SERVER-61763 Add query related metrics to serverSt... Closed
is related to SERVER-68847 Include "Query Framework" information... Closed
Backwards Compatibility: Fully Compatible
Participants:

 Description   

It would be helpful to distinguish whether active queries are using the SBE or classic engines, in case there's ever a problem where SBE specifically is misbehaving, versus the classic engine, when both are running on a mongod depending on the query. 

I did some investigation into adding flags to currentOp output, so I've added some notes below in case it is helpful.

------------------------------------------------------

The info should be carried across to getMore cmds, so it looks like the info will need to hook into/through the ClientCursor (perhaps a flag on the PlanExecutor the ClientCursor holds). The decision whether to use SBE appears to take place in getExecutor. So perhaps inside the getSlotBasedExecutor where OpDebug info is set (this will ultimately go into <db>.system.profile after the operation is done), we can add setting a flag on CurOp.

I'm unfamiliar with if there are any nesting problems to worry about, e.g. the DBDirectClient and leaving CurOp flags set when no longer running a query, or perhaps even subsequently running a query that uses the classic engine. Granted, that sounds like a problem for internal server operations, rather than user initiated operations. I'm not sure what the status quo is for this type of thing.



 Comments   
Comment by Githook User [ 14/Nov/22 ]

Author:

{'name': 'Alyssa Wagenmaker', 'email': 'alyssa.wagenmaker@mongodb.com', 'username': 'awagenmaker'}

Message: SERVER-68803 Add whether SBE is in use to currentOp output
Branch: master
https://github.com/mongodb/mongo/commit/d5a618c24e4734f7118ebaf4c186ac855916d99a

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