[DOCS-1808] Comment on: "reference/command/cloneCollectionAsCapped.txt" Created: 13/Aug/13  Updated: 11/Jan/17  Resolved: 27/Jul/16

Status: Closed
Project: Documentation
Component/s: manual
Affects Version/s: mongodb-2.4
Fix Version/s: 01112017-cleanup

Type: Improvement Priority: Major - P3
Reporter: Thomas Hjorslev Assignee: Unassigned
Resolution: Won't Fix Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 7 years, 29 weeks ago

 Description   

The documentation for convertToCapped states that "This command obtains a global write lock and will block other operations until it has completed". But the documentation for cloneCollectionAsCapped does not contain this warning, although it does indeed seem like a global write lock is acquired.

In a related note, it seems excessive to require a server wide lock in order to perform this operation. At least the documentation should contain some information about how to regain control over the server. Currently, all of our management tools time out or fails with "couldn't get readlock to open admin db".



 Comments   
Comment by Emily Hall [ 27/Jul/16 ]

Closed by Emily Hall for Housekeeping on 7/27/16.
Please create a new ticket if for prioritization.

Thank you!

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