[SERVER-12975] Write command to mongos with invalid NS fails differently with mixed versions Created: 28/Feb/14  Updated: 11/Jul/16  Resolved: 10/Mar/14

Status: Closed
Project: Core Server
Component/s: Sharding, Write Ops
Affects Version/s: 2.6.0-rc0
Fix Version/s: 2.6.0-rc2

Type: Bug Priority: Major - P3
Reporter: Mathias Stearn Assignee: Siyuan Zhou
Resolution: Done Votes: 0
Labels: 26qa
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Operating System: ALL
Participants:

 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"
                }
        ]
}



 Comments   
Comment by Githook User [ 10/Mar/14 ]

Author:

{u'username': u'visualzhou', u'name': u'Siyuan Zhou', u'email': u'siyuan.zhou@mongodb.com'}

Message: SERVER-12975 Write command to mongos checks invalid NS
Branch: master
https://github.com/mongodb/mongo/commit/629de3b0f493ad7517b2aecd6ec616df015f53dc

Comment by Mathias Stearn [ 28/Feb/14 ]

Added info about collection to Description field.

Comment by Greg Studer [ 28/Feb/14 ]

The collection name itself would be useful here - it'll narrow down the validation that's not happening.

Generated at Thu Feb 08 03:30:15 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.