Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-60324

Looking up already-removed index in IndexCatalogImpl::_logInternalState

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.2.0
    • None
    • None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2021-10-18
    • 31

    Description

      If there is unexpectedly still indexes present after removing all indexes via IndexCatalogImpl::dropAllIndexes, we log information about the leftover state in IndexCatalogImpl::_logInternalState. However, as a part of this, we log the indexes that we should have already dropped, including calling Collection::getIndexSpec for those indexes. This is incorrect since we cannot call this function for an index that no longer exists. We can fix this by either not logging this at all, or by first checking Collection::isIndexPresent.

      Attachments

        Activity

          People

            gregory.noma@mongodb.com Gregory Noma
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: