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

DocumentSourceCursor should destroy its PlanExecutor while holding the collection lock

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Query 2016-11-21, Query 2016-12-12, Query 2017-01-23, Query 2017-02-13, Query 2017-03-27, Query 2017-04-17
    • 0

      Note: This is only an issue after the changes from SERVER-25005 because the "inner" plan executor underlying the aggregation pipeline is now registered in the collection's cursor manager.

      Deregistering a PlanExecutor requires accessing the CursorManager of a Collection. We must hold a lock on the collection in order to prevent the collection from going away while deregistering the plan executor.

            Assignee:
            charlie.swanson@mongodb.com Charlie Swanson
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            6 Start watching this issue

              Created:
              Updated:
              Resolved: