[SERVER-36322] NamespaceSerializer lock should be used for dropCollection Created: 27/Jul/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.2, 4.1.2

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

Issue Links:
Backports
Depends
Duplicate
is duplicated by SERVER-31643 Make drop collection in concurrency w... Closed
Related
related to SERVER-47422 Use NamespaceSerializer when taking d... Closed
related to SERVER-49145 Prevent distributed lock timeouts in ... Closed
is related to SERVER-36433 NamespaceSerializer lock should be us... Closed
Backwards Compatibility: Fully Compatible
Operating System: ALL
Backport Requested:
v4.0
Sprint: Sharding 2018-08-13
Participants:
Linked BF Score: 17

 Description   

NamespaceSerializer was added to createCollection to prevent unneeded timeouts occurring when several create operations in parallel try to acquire the same distributed lock. The same should be applied to dropCollection.



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

Author:

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

Message: SERVER-36322 NamespaceSerializer lock should be used for dropCollection

(cherry picked from commit 7c2f9059b349fc01ab24130de4a9c5d0277516a3)
Branch: v4.0
https://github.com/mongodb/mongo/commit/4aeeb5baaca7122162db2899904e264144bc85ca

Comment by Githook User [ 03/Aug/18 ]

Author:

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

Message: SERVER-36322 NamespaceSerializer lock should be used for dropCollection
Branch: master
https://github.com/mongodb/mongo/commit/7c2f9059b349fc01ab24130de4a9c5d0277516a3

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