[SERVER-85536] [4.4] removing unindexed unique partial index entries generates write conflicts Created: 22/Jan/24 Updated: 25/Jan/24 Resolved: 25/Jan/24 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 4.4.23 |
| Fix Version/s: | 4.4.29 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Benety Goh | Assignee: | Louis Williams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||
| Assigned Teams: |
Storage Execution
|
||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||
| Operating System: | ALL | ||||||||||||||||||||||||||||
| Sprint: | Execution Team 2024-02-05 | ||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||
| Description |
|
In 4.4, removing index keys from a unique partial index that do not satisfy the partial filter may generate write conflicts for concurrent storage transactions that are also removing unindexed entries. This is largely due to existing logic intended to work with pre-4.2 background indexing operations, which is no longer a concern since background index builds were deprecated by hybrid index builds in 4.2. Some of this write conflicting behavior was removed in 5.0 as part of the cleanup in Prior to 4.4.23 (and |
| Comments |
| Comment by Githook User [ 25/Jan/24 ] |
|
Author: {'name': 'Louis Williams', 'email': 'louiswilliams@users.noreply.github.com', 'username': 'louiswilliams'}Message: GitOrigin-RevId: aa3ee1090934fab545784759b95ec8fab5e38707 |
| Comment by Steven Vannelli [ 23/Jan/24 ] |
|
britt.snyman@mongodb.com maria.prinus@mongodb.com - we're marking this as 4.4 Required because it is something we want to get into 4.4 and wanted to put it on your radar. |