Details
-
Task
-
Status: Closed
-
Major - P3
-
Resolution: Fixed
-
None
-
None
-
None
-
KANBAN BUCKET
Description
Description:
listCollections only requires intent locks (MODE_IS).
Scope of changes:
- 4.0.txt
- db.CollectionInfos + db.collectionNames (double check how we phrase nameOnly – IS lock)
- command/listCollections.txt
Impact to other docs outside of this product:
MVP:
Resources:
Engineering Ticket Description:
Currently the listCollections command requires a MODE_S lock on the database it's run on. When any transaction is active on that database, it will generally have a MODE_IX lock on a collection. This will conflict with the MODE_S lock on the database, causing listCollections to block until the transaction is finished or aborted.
It should be sufficient to have the MODE_IS lock on the database, as long as each collection is locked as its details are gathered.
Attachments
Issue Links
- documents
-
SERVER-34243 listCollections should not require a MODE_S database lock
-
- Closed
-
- is related to
-
DOCS-11593 Docs for SERVER-34244: listCollections should support a nameOnly option
-
- Closed
-