[DOCS-11642] Docs for SERVER-34243: listCollections should not require a MODE_S database lock Created: 23/Apr/18  Updated: 29/Oct/23  Resolved: 11/Jun/18

Status: Closed
Project: Documentation
Component/s: None
Affects Version/s: None
Fix Version/s: 3.7.6, 3.6.21

Type: Task Priority: Major - P3
Reporter: Kay Kim (Inactive) Assignee: Kay Kim (Inactive)
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-34243 listCollections should not require a ... Closed
Related
is related to DOCS-11593 Docs for SERVER-34244: listCollection... Closed
Participants:
Days since reply: 5 years, 35 weeks, 2 days ago
Epic Link: DOCS: 4.0 Server

 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.



 Comments   
Comment by Githook User [ 11/Jun/18 ]

Author:

{'username': 'kay-kim', 'name': 'kay', 'email': 'kay.kim@10gen.com'}

Message: DOCS-11642: listCollection and IS lock
Branch: master
https://github.com/mongodb/docs/commit/6639497f8cd7410ddf4626120e8d85ce8a358ce0

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