[SERVER-71950] Fail and log the operation when out-of-order keys are detected in WiredTiger Created: 07/Dec/22 Updated: 29/Oct/23 Resolved: 31/Jan/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.2.24, 4.4.19, 5.0.15, 6.3.0-rc0, 6.0.5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Will Korteland | Assignee: | Gregory Wlodarek |
| 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 | ||||||||||||||||||||||||
| Backport Requested: |
v6.2, v6.0, v5.0, v4.4, v4.2
|
||||||||||||||||||||||||
| Sprint: | Execution Team 2022-12-26, Execution Team 2023-02-06 | ||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Description |
|
During an index rebuild, IndexBuildsManager::startBuildingIndexForRecovery will go back to the beginning in the case of a write conflict exception in a partial batch. This can lead to "infinite looping" behaviour for some classes of cursor problems (see HELP-40283). It should do something that makes failures a bit clearer, e.g. having a retry limit if the occasional write conflict is expected, or possibly aborting the build for that index. This issue can occur when data corruption is present such that keys returned from the storage engine are not in ascending order. Update |
| Comments |
| Comment by Githook User [ 11/Feb/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit b2085e2d422278733bb6925614eb0c2f36348034) |
| Comment by Githook User [ 10/Feb/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit b2085e2d422278733bb6925614eb0c2f36348034) |
| Comment by Githook User [ 10/Feb/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit b2085e2d422278733bb6925614eb0c2f36348034) |
| Comment by Githook User [ 10/Feb/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: (cherry picked from commit b2085e2d422278733bb6925614eb0c2f36348034) |
| Comment by Githook User [ 31/Jan/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Githook User [ 03/Jan/23 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: Revert " This reverts commit 6abf3a43cd8419d914627cbeb9fa54e8d2a46f11. |
| Comment by Githook User [ 13/Dec/22 ] |
|
Author: {'name': 'Gregory Wlodarek', 'email': 'gregory.wlodarek@mongodb.com', 'username': 'GWlodarek'}Message: |
| Comment by Will Korteland [ 07/Dec/22 ] |
|
(cc'ing gregory.wlodarek@mongodb.com just so you know I ended up making the ticket) |