[SERVER-63054] Acquires MODE_IX lock during collMod index scan to allow stepdown kills the operation Created: 27/Jan/22 Updated: 29/Oct/23 Resolved: 28/Jan/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.3.0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Yuhong Zhang |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Execution Team 2022-02-07 |
| Participants: |
| Description |
|
Currently the scan holds a MODE_IS lock which will continue during a stepdown doing waste of work. Although the index scan itself doesn't modify the data in the collection, it has the intention to later write to the collection with the collMod convert to unique. This will still allow concurrent writes to the collection. |
| Comments |
| Comment by Githook User [ 28/Jan/22 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'danielzhangyh@gmail.com', 'username': 'YuhongZhang98'}Message: |