[SERVER-84181] Skip creating oplog entry for unreplicated collections Created: 14/Dec/23  Updated: 02/Feb/24  Resolved: 17/Jan/24

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: Huayu Ouyang Assignee: Wenbin Zhu
Resolution: Fixed Votes: 0
Labels: repl-shortlist
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-81613 Make OpObservers take less time when ... Closed
Assigned Teams:
Replication
Backwards Compatibility: Fully Compatible
Sprint: Repl 2024-01-08, Repl 2024-01-22
Participants:

 Description   

Similar to SERVER-81613 (which was for CRUD operations), we should skip creating an oplog entry in onCreateCollection for unreplicated collections. Currently we create a MutableOplogEntry and then only check if the collection is unreplicated here, but we should skip creating the oplog entry in the first place



 Comments   
Comment by Max Hirschhorn [ 02/Feb/24 ]

I believe this ticket also addressed how the changes from 2617116 as part of SERVER-73601 made it so even standalone mongod processes would log about writing oplog entries.

Comment by Githook User [ 17/Jan/24 ]

Author:

{'name': 'Wenbin Zhu', 'email': 'wenbin.zhu@mongodb.com', 'username': 'WenbinZhu'}

Message: SERVER-84181 Skip creating oplog entry for unreplicated collections. (#17948)

GitOrigin-RevId: 854d2e69f0385c129dc86b686dc1d5ed1ec780d6
Branch: master
https://github.com/mongodb/mongo/commit/712ed2d778874ebaf832fcc5b19e1073d2819ae0

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