[SERVER-60493] Add pinned oplog timestamp to logging when oplog truncation occurs Created: 06/Oct/21  Updated: 29/Oct/23  Resolved: 07/Oct/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: 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:
Related
Backwards Compatibility: Fully Compatible
Sprint: Execution Team 2021-10-18
Participants:
Linked BF Score: 21

 Description   

This will help with debugging. I've got a bug where too much oplog was truncated, so I'm hoping this value can shed some light onto what's going on.



 Comments   
Comment by Githook User [ 07/Oct/21 ]

Author:

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

Message: SERVER-60493 Add the pinnedOplog timestamp to the oplog truncation thread's logging
Branch: master
https://github.com/mongodb/mongo/commit/b348fc023c809d9594b37d12a0640f3bdb6efe20

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