[DOCS-10992] convertToCapped is missing the 'global write lock' warning Created: 07/Nov/17  Updated: 30/Oct/23  Resolved: 20/Nov/17

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

Type: Bug Priority: Major - P3
Reporter: Adrien Siebert Assignee: Kevin Albertson
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Problem/Incident
is caused by DOCS-4502 Remove 'global write lock' mention fr... Closed
Related
related to SERVER-15723 Avoid G_X lock for rename_collection ... Closed
related to SERVER-15826 ConvertToCapped appears to be taking ... Closed
Participants:
Days since reply: 6 years, 12 weeks, 2 days ago
Story Points: 0.25

 Description   

http://docs.mongodb.org/manual/reference/command/convertToCapped/ does not mention that the command acquires a global write lock on the server, with all the dire consequences this can have on a live instance.
The guide about "Converting a collection to capped" does mention it.

It appears the mention was removed in DOCS-4502 allegedly because "This is no longer true in 2.8 due to SERVER-15826" back in 2014.
I assume there was some confusion, as I found no evidence of the lock being actually removed, though it does switch to a DB lock in some cases after SERVER-15723 - a very recent change (3.4.10/3.5.10).

If that report is confirmed, might a revert of mongodb/docs 72f694e be enough?



 Comments   
Comment by Githook User [ 20/Nov/17 ]

Author:

{'name': 'Kevin Albertson', 'username': 'kevinAlbs', 'email': 'kevin.albertson@10gen.com'}

Message: DOCS-10992 capped commands take DB_X locks
Branch: master
https://github.com/mongodb/docs/commit/9b1f13cfa5edab3a68cc574b3f3b768d9131026a

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