thread OperationContext* down through ClusterClientCursor's next() and kill() methods

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Done
    • Priority: Major - P3
    • 3.5.3
    • Affects Version/s: 3.5.2
    • Component/s: Querying, Sharding
    • None
    • Fully Compatible
    • Sharding 2017-02-13
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      This removes the need for the AsyncResultsMerger to store an OperationContext*, which it uses to schedule finds, getMore's, and killCursors on remote shards.

      This makes it easier to deal with the RouterStageMerge being split into two parts (sending the finds to establish cursors, and sending the getMore's to pull and merge results), where both parts need to access the OperationContext*.

            Assignee:
            Esha Maharishi (Inactive)
            Reporter:
            Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: