New shard with new database can be ignored by change streams

XMLWordPrintableJSON

    • 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
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      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.

              Assignee:
              Bernard Gorman
              Reporter:
              Charlie Swanson
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: