[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: | |||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 3 years, 43 weeks, 6 days ago | ||||
| Epic Link: | DOCSP-1769 | ||||
| Description |
DescriptionIn the document How Granular Are Locks in MongoDB it says:
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, Scope of changesImpact to Other DocsMVP (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: |
| Comment by Githook User [ 09/Apr/20 ] |
|
Author: {'name': 'Kay Kim', 'email': 'kay.kim@10gen.com', 'username': 'kay-kim'}Message: |