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

Make unpin of ClientCursor exception safe for getMore on aggregation cursors

XMLWordPrintableJSON

    • Type: Icon: Improvement Improvement
    • Resolution: Unresolved
    • Priority: Icon: Major - P3 Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Querying
    • Labels:
      None
    • Query Execution
    • Fully Compatible
    • Quint Iteration 7

      Locking behavior for getMore on an aggregation cursor is special. In particular, MODE_IS database and collection locks are only acquired in order to unpin the ClientCursor.

      The implementation of this is currently not exception safe: currently, if an exception is thrown during the execution of the query, the ClientCursor will be unpinned out of the locks (see TODO in the code).

            Assignee:
            backlog-query-execution [DO NOT USE] Backlog - Query Execution
            Reporter:
            david.storch@mongodb.com David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: