[SERVER-33990] Add logging around oplog truncation and reading oplog optime after rollback Created: 19/Mar/18  Updated: 29/Oct/23  Resolved: 21/Mar/18

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: None
Fix Version/s: 3.7.4

Type: Task Priority: Major - P3
Reporter: William Schultz (Inactive) Assignee: William Schultz (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: Repl 2018-03-26
Participants:
Linked BF Score: 0

 Description   

We should add additional logging around the details of oplog truncation and how we load the optime from the oplog after rollback.



 Comments   
Comment by Eric Milkie [ 26/Apr/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}

Message: SERVER-34091 Change boolean type to int
Branch: master
https://github.com/mongodb/mongo/commit/68e4e5b84d700b26d0b3333f91ea72588c982c32

Comment by Githook User [ 21/Mar/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}

Message: SERVER-33990 Fix typo in bgsync.cpp
Branch: master
https://github.com/mongodb/mongo/commit/aa90ee2e4d67c93abcbf19105cbbef22ba20e44f

Comment by Githook User [ 21/Mar/18 ]

Author:

{'email': 'william.schultz@mongodb.com', 'name': 'William Schultz', 'username': 'will62794'}

Message: SERVER-33990 Add logging around oplog truncation and reading oplog optime after rollback
Branch: master
https://github.com/mongodb/mongo/commit/b0b84aa0703b55a56e05d1344334b566097249c3

Generated at Thu Feb 08 04:35:13 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.