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

Investigate if a gap in cursor ownership allows cursor leaks during error paths

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Aggregation Framework
    • None
    • Query Execution
    • Fully Compatible

    Description

      During development on SERVER-24978 we realized there's a time between establishing cursors on mongod and establishing the merging half of the pipeline on a merging shard where the cursors aren't logically owned by anyone. We suspect that an error encountered at this specific moment would cause the cursors to be abandoned on the shards, eventually cleaned up by the cursor timeout thread, but effectively leaked.

      We should investigate whether or not this is actually the case, and see if we can fix it if so.

      Attachments

        Activity

          People

            backlog-query-execution Backlog - Query Execution
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated: