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

Aggregate with collectionUUID on sharded cluster can incorrectly omit the actual collection

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 6.0.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Fully Compatible
    • ALL
    • Execution Team 2022-04-04

      For example if the primary shard does not own any chunks for the collection being queried, $indexStats will not target that shard. Then if the actual collection is unsharded, the actualCollection field of the CollectionUUIDMismatch will not be populated even though it should be. More generally, this can occur if there are no shards that contain chunks for both collections. This should be able to be solved with the same approach as SERVER-63285.

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

              Created:
              Updated:
              Resolved: