[SERVER-38449] TemporaryKVRecordStore should fail with a fassert rather than an invariant Created: 07/Dec/18  Updated: 29/Oct/23  Resolved: 12/Dec/18

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

Type: Improvement Priority: Major - P3
Reporter: Benety Goh Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to SERVER-37843 Create an index reaper for two-phase ... Closed
is related to SERVER-38187 Ability to create a temporary RecordS... Closed
Backwards Compatibility: Fully Compatible
Sprint: Storage NYC 2018-12-17
Participants:

 Description   

When TemporaryKVRecord fails to remove the temporary ident in its destructor, it aborts the program with an invariant. This is inconsistent with the treatment in KVDropPendingIdentReaper which fails with an fassert.



 Comments   
Comment by Githook User [ 12/Dec/18 ]

Author:

{'name': 'Benety Goh', 'email': 'benety@mongodb.com', 'username': 'benety'}

Message: SERVER-38449 convert invariant in TemporaryKVRecordStore to fassert
Branch: master
https://github.com/mongodb/mongo/commit/c0b48bee20c8383f08902d2bd338010e95312fa6

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