[SERVER-66924] Dropping config.system.change_collection attempts to write change event about itself being dropped Created: 01/Jun/22  Updated: 29/Oct/23  Resolved: 23/Jun/22

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

Type: Bug Priority: Major - P3
Reporter: Gregory Noma Assignee: Rishab Joshi (Inactive)
Resolution: Fixed Votes: 0
Labels: pm-2334-m1
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: QE 2022-06-13, QE 2022-06-27
Participants:
Linked BF Score: 173

 Description   

If you issue a drop of the config.system.change_collection collection while it is still enabled, it will try to write a change event about the drop of itself. Since the change event write occurs after the event itself, in this scenario it results in attempting to do the change event write after the change event collection has been dropped.



 Comments   
Comment by Githook User [ 23/Jun/22 ]

Author:

{'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}

Message: SERVER-66924 Avoid inserting to the change collection that is already dropped.
Branch: davish/SERVER-63099
https://github.com/mongodb/mongo/commit/c41d2317c3c560114a090338658d21cba7b86171

Comment by Githook User [ 23/Jun/22 ]

Author:

{'name': 'Rishab Joshi', 'email': 'rishab.joshi@mongodb.com', 'username': 'rishvin'}

Message: SERVER-66924 Avoid inserting to the change collection that is already dropped.
Branch: master
https://github.com/mongodb/mongo/commit/c41d2317c3c560114a090338658d21cba7b86171

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