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

DropDatabaseCoordinator should only report a single drop event per dropped collection through the Primary Shard oplog

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 6.3.0-rc0
    • None
    • None
    • None
    • Fully Compatible
    • Sharding EMEA 2022-11-28, Sharding EMEA 2022-12-12

    Description

      When a nss.dropDatabase() command gets executed on a sharded collection, every shard participating in the DDL is currently adding an internal {op: drop}  event to its oplog for each collection that gets locally dropped.

      This may generate some ambiguity from the perspective of a mongos serving a droppedDb.coll.watch() request (which is collecting oplog events from multiple shards) to establish the exact point in time at which the change stream may be considered as invalidated.

      To solve this, each non-primary shard should hide the "local collection drop" event by marking the related oplog entry with the fromMigrate option.

      Attachments

        Activity

          People

            paolo.polato@mongodb.com Paolo Polato
            paolo.polato@mongodb.com Paolo Polato
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: