[SERVER-47692] SharedBufferFragmentAllocator should discard its buffer on destruction if the build was incomplete Created: 21/Apr/20  Updated: 29/Oct/23  Resolved: 22/Apr/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: Louis Williams Assignee: Louis Williams
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-47605 Single-phase index builds should only... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-05-04
Participants:

 Description   

If a SharedBufferFragmentBuilder is started but not finished due to an error thrown by a caller, the owning SharedBufferFragmentAllocator should discard the buffer.

This causes this invariant to hit if a subsequent buffer is constructed on the same SharedBufferFragmentBuilder.



 Comments   
Comment by Githook User [ 22/Apr/20 ]

Author:

{'name': 'Louis Williams', 'email': 'louis.williams@mongodb.com', 'username': 'louiswilliams'}

Message: SERVER-47692 SharedBufferFragmentAllocator should discard its buffer on destruction if the build was incomplete
Branch: master
https://github.com/mongodb/mongo/commit/f0cd3af849b8725d393df2f5f95f09216d9182c5

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