[SERVER-48303] biggie engine key generator can generate duplicate record id Created: 19/May/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

Issue Links:
Related
related to SERVER-48945 Move lazy RecordId initialization for... Backlog
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-06-15, Execution Team 2020-06-29
Participants:

 Description   

Biggie engine keeps the radix tree in the recovery unit but the counter for the key generator is in the record store.
Record stores that get created and destroyed while the recovery unit is alive may generate keys for the radix store that already exists.

This happens when loadCatalog() recreates catalog entries for orphaned idents



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

Author:

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

Message: SERVER-48303 Lazily initialize highest record id in Biggie record store like how WT does it
Branch: master
https://github.com/mongodb/mongo/commit/c7752f1b5852d2d5acbf36aea26dd07819398343

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