[SERVER-81442] Poke WT oplog reclamation thread periodically Created: 26/Sep/23  Updated: 30/Nov/23  Resolved: 14/Nov/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.3.0-rc0, 7.0.5, 6.0.13, 5.0.24

Type: Improvement Priority: Major - P3
Reporter: Dan Larkin-York Assignee: Daotang Yang
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
Assigned Teams:
Storage Execution
Backwards Compatibility: Fully Compatible
Backport Requested:
v7.0, v6.0, v5.0
Sprint: Execution Team 2023-11-13, Execution Team 2023-11-27
Participants:

 Description   

Currently we only perform checks (in the oplog reclamation thread) as to whether the WT oplog can be truncated when a) we finish sampling the oplog during recovery, b) we resize the oplog, or c) we create a new oplog stone.

In cases where the oplog size exceeds the limit, but the oplog window is smaller than the configured retention period, we may (correctly) choose not to truncate the oplog at a given point in time. However, if enough time passes so that the oplog window grows, but one of the three triggering events described above does not occur, we currently will not truncate the oplog. For instance, during a long period of low write activity, we may not generate a new oplog stone, leaving the oplog untruncated for a long period of time.



 Comments   
Comment by Githook User [ 30/Nov/23 ]

Author:

{'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}

Message: SERVER-81442 Poke WT oplog reclamation thread periodically

(cherry picked from commit 068fc443154eee243bb24802f96baa5a4d370ddd)
Branch: v7.0
https://github.com/mongodb/mongo/commit/4d5f5a9b97c4e439af273e2bfb05b5e167228aa7

Comment by Githook User [ 29/Nov/23 ]

Author:

{'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}

Message: SERVER-81442 Poke WT oplog reclamation thread periodically

(cherry picked from commit 068fc443154eee243bb24802f96baa5a4d370ddd)
Branch: v6.0
https://github.com/mongodb/mongo/commit/291ec628dc99ab914f1c546331cb4684308b3a81

Comment by Githook User [ 29/Nov/23 ]

Author:

{'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}

Message: SERVER-81442 Poke WT oplog reclamation thread periodically

(cherry picked from commit 068fc443154eee243bb24802f96baa5a4d370ddd)
Branch: v5.0
https://github.com/mongodb/mongo/commit/3d5a38fd395ee2547afa48f051340022700d41a4

Comment by Githook User [ 14/Nov/23 ]

Author:

{'name': 'Daotang Yang', 'email': 'daotang.yang@mongodb.com', 'username': ''}

Message: SERVER-81442 Poke WT oplog reclamation thread periodically
Branch: master
https://github.com/mongodb/mongo/commit/068fc443154eee243bb24802f96baa5a4d370ddd

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