Normally, when an index is dropped, it is also invalidated in the CollectionInfoCache.
It looks like refreshEntry, which is used by collMod, will delete the IndexCatalogEntry, but never invalidates the index from the cache. This means that the cache may still attempt to use a refreshed index because it is not aware the original index entry was ever deleted.
We should call CollectionInfoCache::droppedIndex to ensure the query planner does not try to use a cached index that has been refreshed with refreshEntry.
- is duplicated by
SERVER-48916 Update plan cache IndexabilityDiscriminator when IndexCatalogEntry is updated