[SERVER-49191] Cache the oplogTruncateAfterPoint in memory and only update it when it changes Created: 30/Jun/20  Updated: 29/Oct/23  Resolved: 01/Feb/21

Status: Closed
Project: Core Server
Component/s: Storage
Affects Version/s: None
Fix Version/s: 4.9.0, 4.4.5

Type: Task Priority: Major - P3
Reporter: Dianna Hohensee (Inactive) Assignee: Dianna Hohensee (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Execution Team 2020-12-28, Execution Team 2021-02-08
Participants:

 Description   

Currently the oplogTruncateAfterPoint is getting redundantly written to even when the value is not changing – imagine a quiet system, still periodically running the code to flush data to disk (nothing to flush, of course), before which we always do an oplogTruncateAfterPoint update regardless of anything.



 Comments   
Comment by Githook User [ 23/Feb/21 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-49191 Cache the oplogTruncateAfterPoint in memory and only update it on-disk when there is a change

(cherry picked from commit 060d4ef8514110ff4d03867b8f704cf9de307905)
Branch: v4.4
https://github.com/mongodb/mongo/commit/ef959be6855bd4d88098a9723af8eee5f73f6faf

Comment by Githook User [ 01/Feb/21 ]

Author:

{'name': 'Dianna Hohensee', 'email': 'dianna.hohensee@mongodb.com', 'username': 'DiannaHohensee'}

Message: SERVER-49191 Cache the oplogTruncateAfterPoint in memory and only update it on-disk when there is a change
Branch: master
https://github.com/mongodb/mongo/commit/060d4ef8514110ff4d03867b8f704cf9de307905

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