[SERVER-11735] dbcase.js/dbcase2.js fail in sharding passthrough if write commands is enabled Created: 15/Nov/13  Updated: 07/Oct/15  Resolved: 16/Sep/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 2.5.3
Fix Version/s: 3.1.9

Type: Task Priority: Major - P3
Reporter: Randolph Tan Assignee: YunHe Wang
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
Backwards Compatibility: Fully Compatible
Sprint: Quint 9 09/18/15
Participants:
Linked BF Score: 0

 Description   

dbcase.js and dbcase2.js pass if run directly without mongos using write commands. It looks like there is a different in the formatting of the returned object:

direct to mongod:

{ "errmsg" : "exception: db already exists with different case other: [dbcasetest_dbnamea] me [dbcasetest_dbnameA]", "code" : 13297, "ok" : 0 }

through mongos:

{ "$err" : "error creating initial database config information :: caused by :: can't have 2 databases that just differ on case have: dbcasetest_dbnamea want to add: dbcasetest_dbnameA", "code" : 13297 }

 Comments   
Comment by Githook User [ 16/Sep/15 ]

Author:

{u'username': u'yhjw88', u'name': u'Yunhe (John) Wang', u'email': u'yunhe.wang@mongodb.com'}

Message: SERVER-11735 Changed dbcase tests to detect write error instead of explicit error code
Branch: master
https://github.com/mongodb/mongo/commit/fa12f702ead7919669e21ff9f532c49a8fec27ef

Comment by YunHe Wang [ 14/Sep/15 ]

Replacing the explicit error code checks with "write failed"

Comment by Githook User [ 07/Oct/14 ]

Author:

{u'username': u'kaloianm', u'name': u'Kaloian Manassiev', u'email': u'kaloian.manassiev@mongodb.com'}

Message: SERVER-11735 Disable dbcase2.js from running under sharding
Branch: master
https://github.com/mongodb/mongo/commit/c4f1421ec0e64832f7d79c5bcd624a8cf93452d9

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