Details
-
Improvement
-
Resolution: Won't Fix
-
Major - P3
-
mongodb-2.4
-
None
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".