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

Cluster aggregate may incorrectly result in CollectionUUIDMismatch if fetching routing info fails

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Fixed
    • None
    • 6.1.1, 6.0.3, 6.2.0-rc0
    • None
    • None
    • Fully Compatible
    • ALL
    • v6.1, v6.0
    • Execution Team 2022-10-31

    Description

      If cluster aggregate's call to sharded_agg_helpers::getExecutionNsRoutingInfo fails, currently we throw CollectionUUIDMismatch if an expected collection UUID was provided. However, if the error is not specifically NamespaceNotFound then it's possible the database actually does exist and we should not throw CollectionUUIDMismatch.

      Attachments

        Issue Links

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: