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

Write command to mongos with invalid NS fails differently with mixed versions

    XMLWordPrintableJSON

Details

    • ALL

    Description

      Filing as a bug since greg_10gen thinks this should be caught by mongos before forwarding command to shards.

      Collection name is "unsharded.errors.$foo". As the db name implies, this is to an unsharded DB.

      2.6 mongos with 2.6 shards:

      { "ok" : 0, "code" : 2, "errmsg" : "invalid collection name at shard0000" }

      2.6 mongos with 2.4 shards:

      {
              "ok" : 1,
              "n" : 0,
              "writeErrors" : [
                      {
                              "index" : 0,
                              "code" : 10093,
                              "errmsg" : "cannot insert into reserved $ collection"
                      }
              ]
      }

      Attachments

        Activity

          People

            siyuan.zhou@mongodb.com Siyuan Zhou
            mathias@mongodb.com Mathias Stearn
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: