[DOCS-13579] drop collections takes collection level lock since 4.2 Created: 09/Apr/20  Updated: 30/Oct/23  Resolved: 09/Apr/20

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: None
Fix Version/s: Server_Docs_20231030

Type: Bug Priority: Major - P3
Reporter: Yaoxing Zhang Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

https://docs.mongodb.com/manual/faq/concurrency/


Issue Links:
Related
Participants:
Days since reply: 3 years, 43 weeks, 6 days ago
Epic Link: DOCSP-1769

 Description   

Description

In the document How Granular Are Locks in MongoDB it says:

Some other operations, such as dropping a collection, still require an exclusive database lock.

On the same page, section What Administrative Commands Lock a Collection, it says drop/dropCollections takes collection level lock.

Former is only true before 4.2.

Regards,
Yaoxing

Scope of changes

Impact to Other Docs

MVP (Work and Date)

Resources (Scope or Design Docs, Invision, etc.)



 Comments   
Comment by Githook User [ 09/Apr/20 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-13579: faq concurrency - small cleanup
Branch: v4.2
https://github.com/mongodb/docs/commit/242487a653043b98a3a3aac6032a27989ff4fa26

Comment by Githook User [ 09/Apr/20 ]

Author:

{'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}

Message: DOCS-13579: faq concurrency - small cleanup
Branch: master
https://github.com/mongodb/docs/commit/eebbbb874f7e36fa55590de3c800a488bd61d149

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