[SERVER-17955] renaming a collection fails in mongos if collection was created by a different mongos Created: 09/Apr/15  Updated: 19/Sep/15  Resolved: 16/Jul/15

Status: Closed
Project: Core Server
Component/s: Sharding
Affects Version/s: 3.0.1
Fix Version/s: None

Type: Bug Priority: Major - P3
Reporter: Jeffrey Yemin Assignee: Kaloian Manassiev
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
is related to JAVA-1757 Fix intermittent failure of driver-as... Closed
Operating System: ALL
Steps To Reproduce:

This is simple to reproduce using two shells, each connected to a different mongos.

  • first shell: db.dropDatabase()
  • second shell: db.createCollection("foo")
  • first shell: db.foo.renameCollection("bar")
Participants:

 Description   

The error message is:

{ 
 "code" : 13140, 
 "ok" : 0.0,
 "errmsg" : "exception: Don't recognize source or target DB" 
}



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

Author:

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

Message: SERVER-17955 Add cross-mongos collection rename test
Branch: master
https://github.com/mongodb/mongo/commit/5ebc97a8dd5905faa12db77f8e55434fd04cb297

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