[DOCS-15061] Investigate changes in SERVER-60848: Log which engine was used for processing a query Created: 24/Jan/22  Updated: 13/Nov/23  Resolved: 08/Sep/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 5.3.0, 5.2.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Alison Huh
Resolution: Gone away Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
backported by DOCS-15064 [BACKPORT] [v5.2] Log which engine wa... Closed
Documented
documents SERVER-60848 Log which engine was used for process... Closed
Participants:
Days since reply: 1 year, 21 weeks, 6 days ago
Epic Link: DOCSP-19447

 Description   
Downstream Change Summary

This patch makes changes to the slow query log line as well as the serverStatus counters. It also changes the system.profile collection, which will have identical fields to the new slow query log line. This change will also be backported to 5.2.

Description of Linked Ticket

Add a field that indicates whether we used classic or SBE for a query. We should backport it to 5.1. At the least we want to see how many queries are exposed to SBE.

Worth considering:

  • just logging a field if the less common case happens (e.g. "sbe")
  • should we use the same field in the future for the optimizer (e.g. "sbe" (executed with sbe) / "cqf" (optimized and executed with cqf)


 Comments   
Comment by Alison Huh [ 08/Sep/22 ]

Will be handling these updates as a part of DOCS-15553.

Comment by PM Bot [ 24/Jan/22 ]

Downstream changes updated for upstream SERVER-60848:
This patch makes changes to the slow query log line as well as the serverStatus counters. It also changes the system.profile collection, which will have identical fields to the new slow query log line. This change will also be backported to 5.2.

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