[SERVER-63562] Skip checking side writes if the index has been already rejecting duplicates during collMod converting to unique Created: 11/Feb/22 Updated: 29/Oct/23 Resolved: 18/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc0 |
| Type: | Improvement | 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-21 |
| Participants: |
| Description |
|
We can skip checking the concurrent writes or just do not install the side write tracker if disallowNewDuplicateKeys=true. But we will need to make sure that the index pointer is not changed between the two times we acquire the locks. |
| Comments |
| Comment by Githook User [ 17/Feb/22 ] |
|
Author: {'name': 'Yuhong Zhang', 'email': 'yuhong.zhang@mongodb.com', 'username': 'YuhongZhang98'}Message: |