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

Ensure CollectionUUIDMismatch error from find command does not omit the actual collection even if unsharded

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Fixed
    • Icon: Major - P3 Major - P3
    • 5.3.0
    • None
    • None
    • None
    • Fully Compatible
    • Execution Team 2022-02-07, Execution Team 2022-02-21

    Description

      Say coll1 (with uuid1) is sharded and coll2 (with uuid2) is unsharded, and the command {find: coll1, filter: ..., collectionUUID: uuid2} is issued where the filter causes the find to target only 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.

      Attachments

        Activity

          People

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

            Dates

              Created:
              Updated:
              Resolved: