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

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

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.5.2
    • 3.5.3
    • Querying, Sharding
    • None
    • Fully Compatible
    • Sharding 2017-02-13

    Description

      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*.

      Attachments

        Issue Links

          Activity

            People

              esha.maharishi@mongodb.com Esha Maharishi
              esha.maharishi@mongodb.com Esha Maharishi
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: