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

Reload shard registry and ensure set of shards hasn't changed when establishing sharded change stream cursors

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Backport Requested:
      v3.6
    • Sprint:
      Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04

      Description

      When establishing a change stream cursor on a sharded collection, mongos will try to establish cursors on all shards it knows about. To protect against a shard being added during this process, mongos will first establish cursors on every shard it knows about from its cache of the shard registry, then after all cursors have been established, it will force the shard registry to reload from the config servers and ensure that no new shards have been added. If a new shard is found, it will need to establish a cursor on any new shards, then redo the shard registry reload and recheck for new shards.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              matthew.russotto Matthew Russotto
              Reporter:
              spencer Spencer Brody (Inactive)
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: