[SERVER-72512] Indexes reported as valid when unable to return inconsistencies due to memory limit Created: 04/Jan/23 Updated: 29/Oct/23 Resolved: 06/Feb/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, 6.2.1 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Yuhong Zhang | Assignee: | Dan Larkin-York |
| 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
|
|||||||||||||||||||||||||||||
| Steps To Reproduce: | Apply the patch
And then run
with
|
|||||||||||||||||||||||||||||
| Sprint: | Execution Team 2023-02-20, Execution Team 2023-02-06 | |||||||||||||||||||||||||||||
| Participants: | ||||||||||||||||||||||||||||||
| Description |
|
We zero out the inconsistencies during validation if it takes more than the memory limit to report them. However, if all inconsistencies are zeroed out, we would return the indexes as valid: true in the indexDetails section, which is confusing. We should at least still flag the index as invalid even if we can't report any of the inconsistencies. Or we should always report at least one inconsistency as the size of one keystring shouldn't cause OOM. |
| Comments |
| Comment by Githook User [ 11/Feb/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: (cherry picked from commit c0e1438cad31e00372a9f9edaee80f9db5a4e8ed) |
| Comment by Githook User [ 11/Feb/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: (cherry picked from commit c0e1438cad31e00372a9f9edaee80f9db5a4e8ed) |
| Comment by Githook User [ 11/Feb/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: (cherry picked from commit c0e1438cad31e00372a9f9edaee80f9db5a4e8ed) |
| Comment by Githook User [ 10/Feb/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: (cherry picked from commit c0e1438cad31e00372a9f9edaee80f9db5a4e8ed) |
| Comment by Githook User [ 10/Feb/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: (cherry picked from commit c0e1438cad31e00372a9f9edaee80f9db5a4e8ed) |
| Comment by Githook User [ 04/Feb/23 ] |
|
Author: {'name': 'Dan Larkin-York', 'email': 'dan.larkin-york@mongodb.com', 'username': 'dhly-etc'}Message: |