[SERVER-77624] Make lock-free multi-acquisitions share the same GlobalLock Created: 31/May/23 Updated: 29/Oct/23 Resolved: 14/Jul/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gomez Ferro | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Sprint: | Sharding EMEA 2023-07-24 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently each lock free-acquired collection holds a GlobalLock. This means that when acquiring multiple collections in a single acquireCollections() call, the global lock is recursively locked. Instead, the global lock should not be recursively locked in this case. Note: In case of multiple different calls to acquireCollection(), it is expected that the global lock gets recursively locked |
| Comments |
| Comment by Githook User [ 14/Jul/23 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |