deleteHaystackIndexesOnUpgrade could dereference inexistent collection

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Major - P3
    • 5.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      When running the setFeatureCompatibility command to upgrade to 5.0, the haystack indexes are deleted. _deleteHaystackIndexesOnUpgrade iterates over the collections for each db. However, if a collection was dropped concurrently before constructing AutoGetCollectionForRead, then the node will crash when dereferencing a null collection.

            Assignee:
            Jordi Serra Torrens
            Reporter:
            Jordi Serra Torrens
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: