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

Sharded cluster fails on mapReduce with output collection when namespace does not yet exist

    XMLWordPrintable

Details

    • Improvement
    • Status: Closed
    • Major - P3
    • Resolution: Works as Designed
    • None
    • None
    • MapReduce
    • None

    Description

      A Java driver test of mapReduce to a non-existent database exposes a difference in behavior between latest builds and the 4.2 release. We're seeing this error:

      {
         "ok": 0.0, 
         "errmsg": "database output-2284299633124 not found", 
         "code": 26, 
         "codeName": "NamespaceNotFound"
      

      on latest sharded clusters. The test succeeds on all released versions of MongoDB.

      Attachments

        Issue Links

          Activity

            People

              backlog-server-query Backlog - Query Team (Inactive)
              jeff.yemin@mongodb.com Jeffrey Yemin
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: