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

Shards do not treat the IGNORED version as "intended sharded"

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • 3.6.15, 4.0.13, 4.2.1
    • 4.2.3, 4.3.3, 4.0.17
    • Sharding
    • None
    • Fully Compatible
    • ALL
    • v4.2, v4.0
    • Sharding 2019-11-18, Sharding 2019-12-02, Sharding 2019-12-30, Sharding 2020-01-13
    • 20

    Description

      Currently, multi-writes in sharding attach shardVersion: IGNORED for multi-writes, which need to be broadcast to more than one shard. Shards, upon receiving shard version IGNORED, unconditionally treat it as "a match" and allow the operation to proceed without triggering a refresh.

      In combination with SERVER-32198, this causes the side effect that if a shard is restarted, multi-writes writes will not trigger a refresh on the shard and the shard will treat the collection as unsharded, thus not writing the shard key to the oplog entries. This in turn impacts any change streams on that collection.

      Attachments

        Issue Links

          Activity

            People

              marcos.grillo@mongodb.com Marcos José Grillo Ramirez
              kaloian.manassiev@mongodb.com Kaloian Manassiev
              Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: