[SERVER-71006] Small window of inconsistency for reads after turning index to multikey Created: 01/Nov/22 Updated: 29/Oct/23 Resolved: 08/Nov/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 5.0.15, 6.0.4, 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Henrik Edin | Assignee: | Henrik Edin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v6.1, v6.0, v5.0
|
||||
| Sprint: | Execution Team 2022-11-14 | ||||
| Participants: | |||||
| Description |
|
When turning an index into multikey we flip the in-memory state in an onCommit handler. This means there is a window between the WT transaction committing and updating the in-memory state where a reader can observe the data but not seeing the index as multi-key. |
| Comments |
| Comment by Githook User [ 09/Jan/23 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: (cherry picked from commit cf648f7bc75f11fa316f6e9fbb737cf9763742c3) |
| Comment by Githook User [ 09/Jan/23 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: (cherry picked from commit cf648f7bc75f11fa316f6e9fbb737cf9763742c3) |
| Comment by Githook User [ 08/Nov/22 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: |