[SERVER-34243] listCollections should not require a MODE_S database lock Created: 30/Mar/18 Updated: 29/Oct/23 Resolved: 21/Apr/18 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Catalog, Storage |
| Affects Version/s: | 3.7.3 |
| Fix Version/s: | 3.7.6, 3.6.21 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Geert Bosch |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||
| Backport Requested: |
v3.6
|
||||||||||||||||||||
| Sprint: | Storage NYC 2018-04-23 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| 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 [ 25/Sep/20 ] |
|
Author: {'name': 'Geert Bosch', 'email': 'geert@mongodb.com', 'username': 'GeertBosch'}Message: (cherry picked from commit bb148ced1999ffee8ebc58cb0fbefd784ac51a1f) Conflicts: |
| Comment by Githook User [ 20/Apr/18 ] |
|
Author: {'email': 'geert@mongodb.com', 'username': 'GeertBosch', 'name': 'Geert Bosch'}Message: |