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

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

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

      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@mongodb.com Esha Maharishi (Inactive)
            Reporter:
            esha.maharishi@mongodb.com Esha Maharishi (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: