Make unpin of ClientCursor exception safe for getMore on aggregation cursors

XMLWordPrintableJSON

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

      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:
            [DO NOT USE] Backlog - Query Execution
            Reporter:
            David Storch
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: