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

Remove read preference from AsyncResultsMerger and $mergeCursors

    • Fully Compatible
    • Query 2018-03-12

      We believe it is the case that once a cursor is established on a node, the read preference does not play a role. For example, if a read preference "primary" query is sent to the primary and a cursor established, then that cursor can still be iterated if the node steps down between the cursor establishment and the getMore.

      This means we no longer have to track the read preference during getMores, except in the specific case of new queries issued during getMores, such as described in SERVER-31665.

            Assignee:
            charlie.swanson@mongodb.com Charlie Swanson
            Reporter:
            charlie.swanson@mongodb.com Charlie Swanson
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: