[SERVER-58476] Do not collect oplog creationString in FTDC Created: 13/Jul/21  Updated: 29/Oct/23  Resolved: 30/Nov/21

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

Type: Improvement Priority: Major - P3
Reporter: Louis Williams Assignee: Daniel Gomez Ferro
Resolution: Fixed Votes: 0
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
related to WT-7534 Investigate FTDC drops during checkpo... Closed
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-10-18, Execution Team 2021-11-29, Execution Team 2021-12-13
Participants:
Linked BF Score: 58

 Description   

FTDC collects storage engine statistics about the oplog. It also collects the "creationString", which is not used, but uses a very expensive "metadata:create" cursor.

In an attempt to speed up FTDC, expose an API that omits the "creationString" field in the response to avoid opening a "metadata:create" cursor.



 Comments   
Comment by Githook User [ 01/Dec/21 ]

Author:

{'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}

Message: SERVER-58476 Add requires_fcv_52 tag to test
Branch: master
https://github.com/mongodb/mongo/commit/40988d0ee89a3c6d1d1175f374dd3a8aa3924cee

Comment by Githook User [ 30/Nov/21 ]

Author:

{'name': 'Daniel Gómez Ferro', 'email': 'daniel.gomezferro@mongodb.com', 'username': 'dgomezferro'}

Message: SERVER-58476 Add `numericOnly' option to collStats, use it for FTDC
Branch: master
https://github.com/mongodb/mongo/commit/d77aec3d56a3ec9be56fb71982729589588a131e

Comment by Louis Williams [ 14/Jul/21 ]

daniel.gottlieb, absolutely, yes, good thought.

Comment by Daniel Gottlieb (Inactive) [ 14/Jul/21 ]

I agree that it's value in FTDC is likely limited. But we may need to take care that doesn't get removed from serverStatus. That does get used to understand what WT options a table was created with.

Generated at Thu Feb 08 05:44:37 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.