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

Make mongos reload the shard registry and re-establish changeStream cursors when encountering a 'retryNeeded' entry

    XMLWordPrintableJSON

Details

    • Fully Compatible
    • v3.6
    • Repl 2017-10-23, Repl 2017-11-13, Repl 2017-12-04
    • 0

    Description

      Shards can return a 'retryNeeded' entry as part of a changeStream on a sharded collection. This happens when the shard recently donated a chunk for this collection to a shard that has no chunks for that collection. When a mongos encounters such an entry it needs to reload the shard registry (to pick up any recently added shards) and then establish changeStream cursors on any new shards it discovers. It will also need to filter out the 'retryNeeded' entry so it never gets back to the client.

      Attachments

        Issue Links

          related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-32085 $changeStream reports incorrect documentKey for unsharded collections that become sharded

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-31028 Reload shard registry and ensure set of shards hasn't changed when establishing sharded change stream cursors

          • Major - P3 - Major loss of function.
          • Closed

          Task - A task that needs to be done. SERVER-31978 Add an invariant that DocumentSourceCloseCursor does not execute on a mongod for a sharded $changeStream

          • Major - P3 - Major loss of function.
          • Closed

          Activity

            People

              matthew.russotto@mongodb.com Matthew Russotto
              spencer@mongodb.com Spencer Brody (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: