[SERVER-61789] Determine if we can avoid global lock upgrade in dbtests/repltests.cpp Created: 29/Nov/21 Updated: 29/Oct/23 Resolved: 08/Jun/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Haley Connelly |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2022-06-13 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently in Base(), we take the global lock in IX mode via dbtests::WriteContextForTests, then later in deleteAll(), we upgrade the global lock to X mode via Lock::GlobalWrite. Given that it's just the test construct, this probably isn't a real problem, but we are working to ban upgrading the global lock in |
| Comments |
| Comment by Githook User [ 08/Jun/22 ] |
|
Author: {'name': 'Haley Connelly', 'email': 'haley.connelly@mongodb.com', 'username': 'haleyConnelly'}Message: |