[DOCS-13070] 4.2.1 Docs for SERVER-43322: Add tracking tools for measuring OplogStones performance Created: 02/Oct/19  Updated: 13/Nov/23  Resolved: 18/Oct/19

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: 4.3.1, 4.2.1, 4.0.14, 3.6.16, 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: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Cloners
is cloned by DOCS-13130 4.4 Docs for SERVER-43322: Add tracki... Closed
Documented
documents SERVER-43322 Add tracking tools for measuring Oplo... Closed
Related
is related to DOCS-13222 Document backport of SERVER-43322 to ... Closed
Participants:
Days since reply: 4 years, 8 weeks ago
Epic Link: DOCS: 4.4 Server Release Work

 Description   

Description

Downstream Change Summary

In this patch, we add the following server parameters: maxOplogTruncationPointsAfterStartup, maxOplogTruncationPointsDuringStartup, minOplogTruncationPoints, oplogTruncationPointSizeMB.

We also add a section to serverStatus called "oplogTruncation", with the fields totalTimeProcessingMicros, processingMethod, truncateCount, and totalTimeTruncatingMicros. The former two fields refer to the total time necessary to process (either by sampling or by scanning) the oplog on start up in order to determine oplog truncation points. The latter two fields refer to oplog truncation count and duration.

Description of Linked Ticket

In order to best educate a solution for SERVER-42175, we should generate some data on start up and truncation performance with respect to different sizes of OplogStones.

We should add server parameters for maximum counts of OplogStones and minimum sizes of OplogStones. Additionally, we should track:

  1. How long oplog sampling takes on start up
  2. Average amount of time spent truncating
  3. Cumulative length of time spent truncating
  4. Cumulative amount of truncate calls

3. and 4. allow us to determine the average amount of time spent truncating.

Scope of changes

  • 4.2 - WT only
  • 4.4 - WT and inMemory (DOCS-13130)

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 18/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-13070: 4.0.14 oplog truncation metrics
Branch: v4.0
https://github.com/mongodb/docs/commit/18f998eb4c0e364b5fe59b2dbddd8bfc5d73d680

Comment by Githook User [ 18/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-13070: 3.6.16 oplog truncation metrics
Branch: v3.6
https://github.com/mongodb/docs/commit/62cfacfa1732945242f1ef74a7b2cb8d18bfda98

Comment by Githook User [ 18/Dec/19 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-13070: 4.0.14 oplog truncation metrics
Branch: v4.0.14
https://github.com/mongodb/docs/commit/8becd46b1cd8a7338c5ef990e638d040d807f05a

Comment by Githook User [ 18/Oct/19 ]

Author:

{'username': 'kay-kim', 'email': 'kay.kim@10gen.com', 'name': 'Kay Kim'}

Message: DOCS-13070: 4.2.1 oplog truncation metrics
Branch: master
https://github.com/mongodb/docs/commit/ff30fdf12c7ba97d7ccd0c87be7595d3b5de4de1

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