[SERVER-29492] Remove use of TaskRunner from CollectionBulkLoader Created: 07/Jun/17  Updated: 30/Oct/23  Resolved: 15/Jun/17

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

Type: Task Priority: Major - P3
Reporter: Andy Schwerin Assignee: Andy Schwerin
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
Backwards Compatibility: Fully Compatible
Participants:
Linked BF Score: 0

 Description   

The CollectionBulkLoader uses a ThreadPool and a TaskRunner to ensure that all of the writes to a collection during a bulk load use the same OperationContext. Because Client and OperationContext can be moved from thread to thread, it is not necessary to dedicate separate threads to each bulk loader. This task is to simplify CollectionBulkLoader by leveraging client-thread rebinding.



 Comments   
Comment by Githook User [ 15/Jun/17 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-29492 Fix use-after-free of OperationContext caused by wrong lifetime of UnreplicatedWritesBlock.
Branch: master
https://github.com/mongodb/mongo/commit/cb1bed9bbc433ad6279e8793e349a1e47446cd15

Comment by Githook User [ 08/Jun/17 ]

Author:

{u'username': u'andy10gen', u'name': u'Andy Schwerin', u'email': u'schwerin@mongodb.com'}

Message: SERVER-29492 Remove task runner from collection bulk loader.
Branch: master
https://github.com/mongodb/mongo/commit/cce59be2127c2f30d9e98b895c9d79e0a3b2e157

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