[SERVER-49930] Log collection name in createCollectionForApplyOps() invariant that collections are not renamed out of the way in steady state replication Created: 27/Jul/20  Updated: 29/Oct/23  Resolved: 01/Dec/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 4.9.0, 4.4.7

Type: Improvement Priority: Major - P3
Reporter: Gregory Noma Assignee: Gregory Wlodarek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-33719 createCollectionForApplyOps should in... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v4.4
Sprint: Execution Team 2020-12-14
Participants:
Linked BF Score: 0

 Description   

There are no logs of the collection name that is attempted to be created before this invariant, so we should log it in the invariant. This will allow for easier diagnosis in case the invariant is hit.



 Comments   
Comment by Githook User [ 17/May/21 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-49930 Log collection name in createCollectionForApplyOps() invariant

(cherry picked from commit 25146a681ed8b646162608c218814b7f183bd89a)
Branch: v4.4
https://github.com/mongodb/mongo/commit/5324d197dd35af728a49e484314626f3545d64ae

Comment by Githook User [ 01/Dec/20 ]

Author:

{'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}

Message: SERVER-49930 Log collection name in createCollectionForApplyOps() invariant
Branch: master
https://github.com/mongodb/mongo/commit/25146a681ed8b646162608c218814b7f183bd89a

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