[SERVER-73101] Avoid upgrading locks in db unit tests Created: 19/Jan/23 Updated: 29/Oct/23 Resolved: 05/Sep/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.2.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Fausto Leyva (Inactive) | Assignee: | Gregory Noma |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Storage Execution NAMER
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2023-03-06, Execution Team 2023-04-03, Execution Team 2023-05-01, Execution Team 2023-05-29, Execution Team 2023-06-12, Execution NAMR Team 2023-09-04, Execution NAMR Team 2023-09-18 | ||||||||
| Participants: | |||||||||
| Description |
|
Specifically: I took a look at the first test and we acquire an IX lock on the collection and then upgrade to a MODE_X lock in "_setFilteringMetadataByUUID". We can acquire the MODE_X lock right away and avoid the upgrade. I assume that the other unit tests will take a similar approach to avoid upgrading locks so I'm lumping them together. |
| Comments |
| Comment by Githook User [ 05/Sep/23 ] |
|
Author: {'name': 'Gregory Noma', 'email': 'gregory.noma@gmail.com', 'username': 'gregorynoma'}Message: |