[SERVER-50221] Keep NoLimitSorter aware of its in-memory data even after calling done() Created: 10/Aug/20  Updated: 29/Oct/23  Resolved: 10/Aug/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: Gregory Noma Assignee: Gregory Noma
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Related
related to SERVER-50920 Resuming index builds from the bulk l... Closed
related to SERVER-49829 Implement spilling for Top K sort in SBE Closed
is related to SERVER-49408 adjust startup to resume index build ... Closed
is related to SERVER-49409 adjust startup to resume index build ... Closed
is related to SERVER-50959 Avoid copying data from the Sorter in... Backlog
is related to SERVER-50095 Augment ResumableIndexBuildTest to en... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Sprint: Execution Team 2020-08-24
Participants:
Linked BF Score: 50

 Description   

SERVER-49829 added this std::move(), but resumable index builds need the NoLimitSorter to remain aware of this in-memory data for if clean shutdown occurs during the bulk load phase without the Sorter having already spilled to disk.



 Comments   
Comment by Githook User [ 10/Aug/20 ]

Author:

{'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}

Message: SERVER-50221 Use shared_ptr to manage NoLimitSorter and InMemIterator in-memory data
Branch: master
https://github.com/mongodb/mongo/commit/6d307c337d5d76e5471e0676fc255cab15aef61a

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