Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12375

Document that in 4.2, an index drop will no longer kill a query which is not using the index

    XMLWordPrintable

Details

    • Task
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • None
    • manual

    Description

      Description

      In all versions of MongoDB prior to 4.2, dropping an index on a particular collection would cause all active queries against that collection to be killed. See SERVER-3964. Work done by the query team's "all cursors globally managed" project has improved this behavior such that dropping an index only kills concurrent queries whose plan actually relies on that index. We may wish to document this improvement (possibly as part of the 4.2 release notes?). I've left a few additional details on SERVER-3964, but feel free to reach out directly to me if you have any questions or require additional information.

      Scope of changes

      • Update dropIndexes and its shell helper with the new behavior
      • Update the release note with the new behavior

       

      Attachments

        Issue Links

          Activity

            People

              ravind.kumar Ravind Kumar (Inactive)
              david.storch@mongodb.com David Storch
              Ravind Kumar Ravind Kumar (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                3 years, 18 weeks ago