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

Ensure CollectionUUIDMismatch error from write commands does not omit the actual collection even if unsharded

    • Type: Icon: Task Task
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • Execution Team 2022-02-21, Execution Team 2022-03-07

      Say coll1 (with uuid1) is sharded and coll2 (with uuid2) is unsharded, and the command {insert: coll1, documents: [{_id: 1}], collectionUUID: uuid2} is issued where the document {_id: 1} belongs on the non-primary shard. Then the returned CollectionUUIDMismatch will erroneously not contain coll2, because it only exists on the primary shard. We should make sure that regardless of which shards are targeted and no matter whether collections are sharded are unsharded, the CollectionUUIDMismatch contains all of the information that it should.

            Assignee:
            gregory.noma@mongodb.com Gregory Noma
            Reporter:
            gregory.noma@mongodb.com Gregory Noma
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: