[SERVER-61786] Determine if we can avoid global lock upgrade in IndexBuildsCoordinatorMongod::setCommitQuorum Created: 29/Nov/21 Updated: 29/Oct/23 Resolved: 11/Mar/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Dan Larkin-York | Assignee: | Fausto Leyva (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Sprint: | Execution Team 2022-03-07, Execution Team 2022-03-21 | ||||||||
| Participants: | |||||||||
| Description |
|
Currently we take the global lock in IS mode due to an AutoGetCollectionForRead, but later upgrade to IX while persisting the change. We would like to avoid this, as upgrading the global lock may lead to deadlocks. It may be safe to simply take the global IX lock prior to the AutoGetCollectionForRead. |
| Comments |
| Comment by Githook User [ 11/Mar/22 ] |
|
Author: {'name': 'Fausto J Leyva', 'email': 'fausto.leyva@mongodb.com', 'username': 'Faustoleyva54'}Message: |