[SERVER-27677] CollectionBulkLoader::_releaseResources() should ensure there is a Client available Created: 13/Jan/17  Updated: 05/Apr/17  Resolved: 18/Jan/17

Status: Closed
Project: Core Server
Component/s: Replication
Affects Version/s: 3.4.1, 3.5.1
Fix Version/s: 3.4.2, 3.5.2

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

Issue Links:
Backports
Depends
is depended on by SERVER-27611 DatabaseCloner::shutdown() does not s... Closed
is depended on by SERVER-27678 CollectionCloner should call _finishC... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Completed:
Backport Requested:
v3.4
Sprint: Repl 2017-01-23
Participants:
Linked BF Score: 0

 Description   

A global Client is required in order to clean up index creation (MultiIndexBlock). _releaseResources() should ensure there is a Client available by calling Client::initThreadIfNotAlready().

_releaseResources() is usually run as a scheduled task on the task runner. this is not the case when it is run during CollectionBulkLoader's destruction.



 Comments   
Comment by Githook User [ 21/Jan/17 ]

Author:

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

Message: SERVER-27677 CollectionBulkLoaderImpl::_releaseResources ensures that a Client is available when destroying MultiIndexBlock

(cherry picked from commit fd6971a17400c37ea6bf6c54ef2c04c25201416d)
Branch: v3.4
https://github.com/mongodb/mongo/commit/17458b93817fdb7963e4323840cffeaf4653b28e

Comment by Githook User [ 18/Jan/17 ]

Author:

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

Message: SERVER-27677 CollectionBulkLoaderImpl::_releaseResources ensures that a Client is available when destroying MultiIndexBlock
Branch: master
https://github.com/mongodb/mongo/commit/fd6971a17400c37ea6bf6c54ef2c04c25201416d

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