[SERVER-43322] Add tracking tools for measuring OplogStones performance Created: 13/Sep/19  Updated: 29/Oct/23  Resolved: 02/Oct/19

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 3.6.16, 4.2.1, 4.3.1, 4.0.14

Type: Bug Priority: Major - P3
Reporter: Maria van Keulen Assignee: Maria van Keulen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Depends
Documented
is documented by DOCS-13070 4.2.1 Docs for SERVER-43322: Add trac... Closed
is documented by DOCS-13130 4.4 Docs for SERVER-43322: Add tracki... Closed
Related
related to SERVER-42175 WiredTigerRecordStore::reclaimOplog c... Closed
related to SERVER-55821 remove next_random_sample_size=1000 c... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.2, v4.0, v3.6
Sprint: Execution Team 2019-09-23, Execution Team 2019-10-07
Participants:
Linked BF Score: 50

 Description   

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.



 Comments   
Comment by Githook User [ 13/Nov/19 ]

Author:

{'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com', 'name': 'Maria van Keulen'}

Message: SERVER-43322 Report oplog processing and truncation data in serverStatus

(cherry picked from commit abaa6d3ce507a3524d5fdea8f95578dd9b08b44c)
(partially cherry picked from commit 62378f4e12644c250ccb894cf6b92d27b77b16fd)
Branch: v3.6
https://github.com/mongodb/mongo/commit/830e5f07bc357e430221f58837bec137f856a00f

Comment by Githook User [ 05/Nov/19 ]

Author:

{'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com'}

Message: SERVER-43322 Report oplog processing and truncation data in serverStatus

(cherry picked from commit dd819eb95636f47f13638259208ae8a69e48ded7)

This backport only includes the serverStatus-related changes of this
commit. It was nontrivial due to differences between the v4.0 and v4.2
branches.
Branch: v4.0
https://github.com/mongodb/mongo/commit/abaa6d3ce507a3524d5fdea8f95578dd9b08b44c

Comment by Githook User [ 10/Oct/19 ]

Author:

{'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com'}

Message: SERVER-43322 Add tunable oplog stone sizes and track truncation speeds

(cherry picked from commit 294a8f68615710b47936d5ee42439d01538ac746)

SERVER-43322 Disallow oplog_sampling.js on inMemory storage enigne

(cherry picked from commit b35dd89515473c97a87b3c06897e8a7ab51c93cc)

This backport was not a straightforward cherry-pick due to SERVER-40168
existing in master and not v4.2.
Branch: v4.2
https://github.com/mongodb/mongo/commit/dd819eb95636f47f13638259208ae8a69e48ded7

Comment by Githook User [ 04/Oct/19 ]

Author:

{'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com'}

Message: SERVER-43322 Disallow oplog_sampling.js on inMemory storage enigne
Branch: master
https://github.com/mongodb/mongo/commit/b35dd89515473c97a87b3c06897e8a7ab51c93cc

Comment by Githook User [ 02/Oct/19 ]

Author:

{'name': 'Maria van Keulen', 'username': 'mvankeulen94', 'email': 'maria.vankeulen@mongodb.com'}

Message: SERVER-43322 Add tunable oplog stone sizes and track truncation speeds
Branch: master
https://github.com/mongodb/mongo/commit/294a8f68615710b47936d5ee42439d01538ac746

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