[SERVER-27381] Remove DBConfig::dropDatabase Created: 12/Dec/16  Updated: 05/Apr/17  Resolved: 13/Dec/16

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.5.1
Fix Version/s: 3.4.2, 3.5.1

Type: Improvement Priority: Major - P3
Reporter: Kaloian Manassiev Assignee: Kaloian Manassiev
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-20854 Don't refresh database and collection... Closed
Backwards Compatibility: Fully Compatible
Backport Requested:
v3.4
Sprint: Sharding 2017-01-02
Participants:

 Description   

The DBConfig::dropDatabase functionality performs blocking reads and writes while holding the database cache entry's mutex. It is only needed for the dropDatabase functionality so it should be moved entirely in there.



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

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-27381 Remove DBConfig::dropDatabase
Branch: v3.4
https://github.com/mongodb/mongo/commit/32f38a3a10517f6a1954615cba3e6d43c47e5867

Comment by Githook User [ 13/Dec/16 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-27381 Remove DBConfig::dropDatabase
Branch: master
https://github.com/mongodb/mongo/commit/b07f96535de47c2da6700074e79ce0ee6eb1ae21

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