[SERVER-48747] Creating multiple collections starting with 'local.oplog' crashes biggie storage engine Created: 11/Jun/20  Updated: 29/Oct/23  Resolved: 18/Jun/20

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

Type: Bug Priority: Major - P3
Reporter: Henrik Edin Assignee: Henrik Edin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-06-29
Participants:

 Description   

RecordStores end up with a dangling pointer to the visibility manager



 Comments   
Comment by Githook User [ 18/Jun/20 ]

Author:

{'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}

Message: SERVER-48747 Biggie visibility manager have the same lifetime as the kv engine

Making sure that RecordStores do not end up with dangling pointers if we create multiple collections starting with "local.oplog."
Branch: master
https://github.com/mongodb/mongo/commit/a8af69397f70903f07b3433c03bfc8b1ab92399f

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