[SERVER-45984] IndexCatalogEntryImpl::isReady() hits invariant in debug builds if the index is not visible in the storage engine Created: 05/Feb/20 Updated: 27/Oct/23 Resolved: 11/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Storage |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Minor - P4 |
| Reporter: | Benety Goh | Assignee: | Eric Milkie |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Sprint: | Execution Team 2020-02-24, Execution Team 2020-03-09, Execution Team 2020-03-23 | ||||
| Participants: | |||||
| Linked BF Score: | 19 | ||||
| Description |
|
In a debug build, if the in-memory catalog is out-of-sync with the on-disk catalog, IndexCatalogEntryImpl::isReady() may fail this debug-only invariant because DurableCatalogImpl::isIndexReady() is fatal to call if the index entry is not visible in the storage engine. |
| Comments |
| Comment by Eric Milkie [ 11/Mar/20 ] |
|
I am proposing that we do no work to fix this problem, as it is only a testing logic issue that hasn't recurred recently. |