Aggregate returns NamespaceNotFound instead of empty result if the db gets dropped

XMLWordPrintableJSON

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: 8.3.0-rc0
    • Component/s: None
    • Query Execution
    • ALL
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      In a sharded cluster with 2 mongoses, the following interleaving will return NamespaceNotFound instead of empty result 

      1. mongos 1 create the collection
      2. mongos 2 runs a find or any other command that requires routing 
      3. mongos 1 drops the db 
      4 mongos 2 runs an aggregate with $listCatalog

      point 4. returns "NamespaceNotFound" 

      I left attached a repro.

      The issue has been discovered during the development of SPM-4330

        1. repro2.js
          0.8 kB
          Enrico Golfieri

            Assignee:
            Unassigned
            Reporter:
            Enrico Golfieri
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated: