[SERVER-36433] NamespaceSerializer lock should be used during drop database Created: 03/Aug/18  Updated: 29/Oct/23  Resolved: 03/Aug/18

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: None
Fix Version/s: 4.0.3, 4.1.2

Type: Bug Priority: Major - P3
Reporter: Janna Golden Assignee: Janna Golden
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Backports
Related
related to SERVER-36322 NamespaceSerializer lock should be us... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Sharding 2018-08-13
Participants:

 Description   

We use the NamespaceSerializer lock to prevent distlock timeouts during create database and collection. We should also do this during drop database.



 Comments   
Comment by Githook User [ 28/Aug/18 ]

Author:

{'name': 'jannaerin', 'email': 'golden.janna@gmail.com', 'username': 'jannaerin'}

Message: SERVER-36433 NamespaceSerializer should be used during dropDatabase

(cherry picked from commit 5b1425734732ef5d8d906fe6cb18d9667df045ed)
Branch: v4.0
https://github.com/mongodb/mongo/commit/910a9125eb2d97b41143d2fde25158b7c799d0e4

Comment by Githook User [ 03/Aug/18 ]

Author:

{'username': 'jannaerin', 'name': 'jannaerin', 'email': 'golden.janna@gmail.com'}

Message: SERVER-36433 NamespaceSerializer should be used during dropDatabase
Branch: master
https://github.com/mongodb/mongo/commit/5b1425734732ef5d8d906fe6cb18d9667df045ed

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