[SERVER-73601] Add info-level logging for DDL oplog entries on primary and secondaries Created: 03/Feb/23  Updated: 29/Oct/23  Resolved: 06/Mar/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 7.0.0-rc0

Type: Task Priority: Major - P3
Reporter: Vishnu Kaushik Assignee: Kaitlin Mahar
Resolution: Fixed Votes: 0
Labels: repl-shortlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
Related
is related to SERVER-74458 Unskip DDL logging test in multiversi... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-03-06
Participants:
Linked BF Score: 168

 Description   

Recently we tried to diagnose a case in which a createCollection oplog entry was missing on the primary / secondaries. From the logs we could see that the createCollection event had occurred on the primary, but we weren't able to determine what the opTime of the event was from the logs. This made it harder to diagnose the problem.

If we want to just log this for createCollection, we can add the opTime information to this log line: https://github.com/10gen/mongo/blob/f9310b523138aa8a79b61797a42748df006cf1b8/src/mongo/db/catalog/database_impl.cpp#L828.

However, it would be nice to log the optimes of all DDL events and possibly CRUD events as well, if the customer has the correct logging level on. This may require logging at the point we actually apply an event to the oplog.



 Comments   
Comment by Githook User [ 05/Mar/23 ]

Author:

{'name': 'Kaitlin Mahar', 'email': 'kaitlin.mahar@mongodb.com', 'username': 'kmahar'}

Message: SERVER-73601 Add info-level logging for DDL oplog entries on primary and secondaries
Branch: master
https://github.com/mongodb/mongo/commit/261711676ca80ce8ce435b09a6ff9384b2c1a82c

Comment by Opal Hoyt [ 06/Feb/23 ]

Consider backport to 4.2

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