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

New shard with new database can be ignored by change streams

    XMLWordPrintable

Details

    • Fully Compatible
    • ALL
    • Query 2019-08-26, Query 2019-09-09, Query 2019-09-23, Query 2019-10-07, Query 2019-10-21, Query 2019-11-04
    • 49

    Description

      We think it is possible to add a shard, create a new database on that shard, and then create one or more unsharded collections on that shard without a change stream noticing that the shard exists.

      The execution machinery uses an oplog entry indicating a migration to detect that a new shard has been added. But in the scenario above there may be no information in any of the shards' oplogs to indicate that a new shard exists.

      Attachments

        Issue Links

          is related to

          Bug - A problem which impairs or prevents the functions of the product. SERVER-44112 The ChangeStream test fails on the latest sharded cluster

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

          Task - A task that needs to be done. SERVER-44039 Improve $changeStream handling of cluster topology changes

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

          Improvement - An improvement or enhancement to an existing feature or task. SERVER-44356 Change Stream latency is determined by config server write rate

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

          Activity

            People

              bernard.gorman@mongodb.com Bernard Gorman
              charlie.swanson@mongodb.com Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: