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

Update plan cache IndexabilityDiscriminator when IndexCatalogEntry is updated

    XMLWordPrintableJSON

Details

    • Icon: Bug Bug
    • Resolution: Duplicate
    • Icon: Major - P3 Major - P3
    • None
    • 3.6.18, 4.0.19
    • None
    • None
    • ALL
    • Query 2020-06-29

    Description

      When the collMod operation updates the TTL of an index, we delete the existing IndexCatalogEntry and create a new one with the updated specifications. The IndexCatalogEntry also owns a CollatorInterface object. The same CollatorInterface object is being used in the plan cache here. So after the IndexCatalogEntry got deleted and re-created, the pointer to collator in CompositeIndexabilityDiscriminator is pointing to a freed memory.

      This seems to have been fixed on 4.2, but still an issue in 3.6 and 4.0.

      Attachments

        Activity

          People

            arun.banala@mongodb.com Arun Banala
            arun.banala@mongodb.com Arun Banala
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: