[SERVER-44479] verify that name is unique when adding entries to the index catalog Created: 07/Nov/19 Updated: 29/Oct/23 Resolved: 13/Dec/19 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Catalog, Index Maintenance |
| Affects Version/s: | None |
| Fix Version/s: | 4.3.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Geert Bosch | Assignee: | Eric Milkie |
| 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 | ||||
| Sprint: | Execution Team 2019-12-02, Execution Team 2019-12-16 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In BF-13897, it appears we've had a case where two index entries had the same name. This should never happen, but could theoretically happen if the in-memory state was out of date with that of the snapshot held by the thread adding the index entry. Add an fassert or invariant to DurableCatalogImpl::prepareForIndexBuild to catch this at the moment it occurs, rather than much later when the duplicate entries cause a problem. |
| Comments |
| Comment by Githook User [ 13/Dec/19 ] |
|
Author: {'name': 'Eric Milkie', 'email': 'milkie@mongodb.com', 'username': 'milkie'}Message: |