[SERVER-81948] Omit DDL oplog entry log messages when in quiet mode Created: 06/Oct/23  Updated: 13/Nov/23  Resolved: 13/Nov/23

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

Type: Task Priority: Major - P3
Reporter: Matthew Kim Assignee: Kaitlin Mahar
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2023-10-16, Repl 2023-10-30, Repl 2023-11-13, Repl 2023-11-27
Participants:

 Description   

In SERVER-73601 we added info-level log messages around DDL oplog entries. These can be noisy in certain use cases and so we should update these messages to not be logged when the "quiet" server parameter is set to true.

Original request:

The Atlas Data Federation team uses mongod for virtual collection queries, and will create/drop a large number of virtual collections over the course of a single query. As a result, over the span of an hour, we've seen ~1.7 million "Wrote oplog entry for drop" and "Added oplog entry for create to transaction" logs. The ADF team would like to reduce log volume and are wondering if these logs can be set to the DEBUG level. 



 Comments   
Comment by Matthew Kim [ 13/Nov/23 ]

kaitlin.mahar@mongodb.com Thanks! And no, we don't have a specific mongod version we need this change in. 

Comment by Githook User [ 13/Nov/23 ]

Author:

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

Message: SERVER-81948 Omit DDL oplog entry log messages when in quiet mode
Branch: master
https://github.com/mongodb/mongo/commit/7b26ff898fc6190c6b0b53ef3a76d21243500c92

Comment by Matthew Kim [ 11/Oct/23 ]

kaitlin.mahar@mongodb.com Yes, not emitting these logs when quiet: true is set would be perfect for us!

Comment by Matthew Kim [ 09/Oct/23 ]

Hi kaitlin.mahar@mongodb.com , thanks for the update. I'm not too familiar with how logging works in mongod. We run mongod with `quiet: true` - would putting these messages into a separate log component potentially let us filter out these logs with `quiet: true`? Based on documentation I'm seeing, I'm not sure what disabling a log component would look like (it only seems like we can set verbosity for log components?), and I'm also not sure how we could go about excluding info-level messages (seems like the lowest verbosity, 0, will just exclude debug messages). Let me know if I'm misunderstanding anything.

Comment by Kaitlin Mahar [ 06/Oct/23 ]

Note these log messages were introduced by SERVER-73601

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